Repository navigation
forge: use the designated release for a tag prefix when it carries the prefix - #252
Merged
Merged
Conversation
With a tag prefix, the lookup skipped the release the maintainer marked as latest and sorted the last 100 releases instead. In a busy monorepo that window is too short: maplibre/martin publishes about ten releases a week across its crates, martin-v1.16.1 already sits at position 44, and the lookup would have found no martin-v release within weeks. The designated release is now used for a prefix too, as long as its tag starts with that prefix. Another product's designated release still falls back to the sorted list.
Contributor
Try this branchThe engine and the scripts resolve independently, so a production script can COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/community-scripts/core/fix/tag-prefix-latest-release \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/debian.sh)"Swap Run a script from a fork as wellcurl -fsSL https://raw.githubusercontent.com/community-scripts/core/fix/tag-prefix-latest-release/tools/run.sh |
bash -s -- https://raw.githubusercontent.com/YOU/DevScripts/your-branch ct/debian.sh \
https://raw.githubusercontent.com/community-scripts/core/fix/tag-prefix-latest-releaseNote that Useful flags while testing
|
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
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.
✍️ Description
With a tag prefix, the lookup skipped the release the maintainer marked as latest and sorted the last 100 releases instead. In a busy monorepo that window is too short: maplibre/martin publishes about ten releases a week across its crates, martin-v1.16.1 already sits at position 44, and the lookup would have found no martin-v release within weeks.
The designated release is now used for a prefix too, as long as its tag starts with that prefix. Another product's designated release still falls back to the sorted list.
🔗 Related Issue
Fixes #
✅ Prerequisites (X in brackets)
API.txtwas updated to match.🛠️ Type of Change (X in brackets)
README,docs/,CONTRIBUTING.md, or other docs.🤖 AI Assistance (X in brackets)