Repository navigation
docs: v2.0.1 tag now resolves; fix older-release pinning advice - #4
Merged
Merged
Conversation
The v2.0.1 tag was moved to its swift-releases commit, so only v2.0.0 and earlier need the older-releases workaround. Pinning the swift-releases branch always gives the latest release, so point older versions at their swift-v<version> commit by revision instead. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BBxgR4mnF8VMVGa42idcxx
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.
Summary
This follows #3. The
v2.0.1tag now points atb42ebae, itsswift-releasescommit, and resolves normally. The README said releases "up to v2.0.1" need the older-releases workaround. This PR changes that to "up to v2.0.0" and notes thatv2.0.1has nosource-v2.0.1tag.It also fixes the workaround itself. Pinning
branch: "swift-releases"always gives the latest release, not the older version the user wants. The README now says to pin theswift-v<version>commit by full revision (the example isswift-v2.0.0,1307a095…) and explains how to look up the commit for other versions.This is a README-only change.
🤖 Generated with Claude Code
https://claude.ai/code/session_01BBxgR4mnF8VMVGa42idcxx
Generated by Claude Code