fix(release): remove fork marker from stable versions - #96
Merged
Conversation
github-actions
Bot
added
vouch:trusted
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What Changed
Stable releases now use plain date-based versions such as 2026.7.2901. The resolver still counts existing +tarik02 tags when selecting the next same-day sequence.
Why
Nightly releases already omit the fork marker. Removing it from stable tags and package versions keeps both channels consistent.
Release PR #95 still contains 2026.7.2901+tarik02 and should not merge first. After this lands, the release workflow will regenerate that branch with 2026.7.2901.
Checklist
Model: GPT-5.6
Harness: T3 Code