Skip to content

Releases: Operation-P-E-A-C-C-E-Robotics/Operation-P-E-A-C-C-E-Robotics.github.io

v2024.06.22

22 Jun 16:56
Compare
Choose a tag to compare

Updates made to the verify-build pipeline so that it is possible for it to run successfully
this change was made in anticipation of my handing the project off to future team members shortly as I am an alumni now

What's Changed

Full Changelog: v2024.02.20...v2024.06.22

v2024.02.20

20 Feb 15:53
b07aecb
Compare
Choose a tag to compare

What's Changed

Full Changelog: v2023.12.27-goLive...v2024.02.20

v2023.12.27-goLive

27 Dec 15:59
Compare
Choose a tag to compare

Go Live!
website officially moved in to production on 12/26/2023
this release marks a "known-good" revert point for future changes as well as establishing the official release schema

Versioning will follow the schema
vYYYY.MM.DD-shortDescription

Example for future reference
v2024.01.06-kickoff
the versioning contains the year in all 4 digits, the month with a leading 0 where needed, the day also with a leading 0 where needed, and a short one or two word description of what the release was created for.

releases should not be single commits, those should be handled on the staging repository and then merged back in to main via pull request with approvals

What's Changed

Full Changelog: pre-release-1...v1.0.X-release

Pre-release 1 Jul 15 2023

15 Jul 15:33
Compare
Choose a tag to compare
Pre-release

Set up automatic security updates with Dependabot
Site is very close to going live. need to have a team meeting about it and meet with mentor in charge of current website

What's Changed

New Contributors

Full Changelog: devlog5-may-27-2023...pre-release-1

Development Log 5 (May 27 2023)

27 May 14:23
Compare
Choose a tag to compare
Pre-release

TinaCMS is working to a useful enough degree, some improvements still to come

Action runners set up in main branch to avoid github issues with cronomiter and triggers

Custom written Admin dashboard retired in place of TinaCMS

Sponsors page still needs to be fixed and presentable

added a light mode setting for pages that are just text and would look bad with White Text on Gray Background

Preparing for move to Production

What's Changed

New Contributors

Full Changelog: devlog4-may-16-2023...devlog5-may-27-2023

Development Log 4 (May 16 2023)

16 May 15:36
Compare
Choose a tag to compare
Pre-release

API Keys are secured
Most Functionality present
Google Calendar and TBA integrations functioning, need to address the problem with cron scheduling
Admin Dashboard mostly functioning
Content turned over to PR to rewrite
Nearly ready for Production

Full Changelog: devlog3-may-2-2023...devlog4-may-16-2023

Development Log 3 (May 2 2023)

02 May 05:06
Compare
Choose a tag to compare
Pre-release
  • API Key is secured and regenerated, no more security threat
  • sponsors updated to reflect reality
  • fancy graphs on robot profiles

TBA Data is now pulled by a github action and stored in JSON files on the branch "gh-actions-tba-data-backend" in the schema of year-data_type.json

this data is retrieved clientside by fetching the data using raw.githubusercontent.com urls that point to the file and are dynamically adjusted to point at the right year

Full Changelog: devlog2-apr-14-2023...devlog3-may-2-2023

Development Log 2 (Apr 14 2023)

15 Apr 00:46
Compare
Choose a tag to compare
Pre-release

Update content
no major changes
better revert point then devlog1 that is the only reason for this release

Full Changelog: devlog1-apr-12-2023...devlog2-apr-14-2023

Development Log 1 (Apr 12 2023)

13 Apr 03:39
Compare
Choose a tag to compare
Pre-release

This release is a known-good revert point.

Working Features:
Robot History - All robots uploaded, some info missing

Current Season - Functioning with potential for new features down the line

Content - Present but needs updating with the exception of the "About Us" page, that has lorem ipsum

Social Media Links - Facebook and Youtube present, others missing

Graphics - Oh its awful please fix

Blue Alliance API v3 READ key publicly committed to repo
must find a way to secure it and then generate a new key (even though it is a read only key it is bad practice to leave an API key publicly commited)