fix(release): stop plugin builds from taking the latest release, and add a switching guide - #2207
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Two fixes to the path a new user actually walks, found while auditing where people who reach the project drop off.
releases/latestserved a plugin, not the appgh release createin the plugin workflow never passed--latest=false, so whichever plugin shipped most recently took the latest spot.releases/latestresolved toplugin-oracle-v1.2.20, a two-hash install note, for anyone landing on the releases page or scripting an install. 162 of the repo's releases are plugin builds, so this was the normal state rather than an edge case.One flag stops it recurring. The current release was re-pointed to v0.65.0 by hand, since the workflow only affects future runs.
build.ymlis deliberately untouched: it pinssoftprops/action-gh-release@v1by SHA andmake_latestonly exists from v2, so adding the input there would risk the release job for no gain. With no plugin release claiming latest, app releases hold it on their own.No page for people switching from another client
The importer reads six other clients and that is documented, but only inside Connection Sharing, which nobody searching for how to move off their current tool would open.
docs/switching.mdxis that page, in Getting Started after Installation.It covers the parts a migration actually trips on:
Screenshots reuse the existing image set. Every image path and internal link was checked to exist.
No CHANGELOG entry: documentation-only, plus a CI change with no user-visible app behaviour.