replace version badges pointing to spago-legacy 0.21 with new Spago version #1326
Conversation
This file contains 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
New version badge points to version specified in https://raw.githubusercontent.com/purescript/spago/refs/heads/master/spago.yaml at path `package.publish.version` Badge configured here: https://shields.io/badges/dynamic-yaml-badge
peterbecich
force-pushed
the
replace-latest-release-readme-badge
branch
from
3c39166 to
2f7922d
Compare
3 tasks
peterbecich
changed the title
|
@f-f please review, this will fix the outdated version numbers at the top of the |
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 of the change
There are two badges in the readme which are misleading.
The first points to
spago@lateston NPM. The second points to the latest GitHub Packages in this repository, which has not been updated fromspago-legacy.This PR updates both badges.
The NPM badge is configured to point to
spago@nexton NPM, via: https://shields.io/badges/npm-version-with-dist-tagPreview:
The badge which replaces the GitHub Packages release version is configured via: https://shields.io/badges/dynamic-yaml-badge
It works by extracting the version from
https://raw.githubusercontent.com/purescript/spago/refs/heads/master/spago.yaml at path
package.publish.versionPreview:
Checklist:
READMEP.S.: the above checks are not compulsory to get a change merged, so you may skip them. However, taking care of them will result in less work for the maintainers and will be much appreciated 😊