feat(release): Creating release scripts for internal and chore release #20286
+914
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: Add
chore-releaseandinternal-releasescripts for automated taggingThis PR introduces two new Python scripts to automate our release tagging process across multiple repositories:
chore-release:ot3-firmware,buildroot,oe-core, andopentronsfor alpha releases.chore_release-X.Y.Zbranch from theopentronsrepository and prompts for user confirmation.--dry-runoption to simulate tagging without making actual changes.internal-release:ot3-firmware,buildroot,oe-core, andopentronsfor internal releases.edgeforopentrons,mainforot3-firmwareandoe-core,opentrons-developforbuildroot).8.8.0) which is converted to an internal version (e.g.,2.8.0).opentronsrepository's existing tags for the given version.internal@v23,internal@2.8.0-alpha.0, andot3@2.8.0-alpha.0.--dry-runoption that efficiently fetches only remote tags (without cloning) to show proposed tags.These scripts aim to streamline our release workflow, reduce manual errors, and ensure consistent tagging across our repositories