fix: resolve action compatibility and release tag issues #12
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 PR fixes two issues that were breaking the tempo-lints GitHub Action:
1. pnpm version conflict in action.yml
Problem: The action hardcoded
version: 9for pnpm, which caused errors in projects usingpackageManager: "pnpm@10.x"becausepnpm/action-setup@v4throws when multiple pnpm versions are specified.Fix: Replace
pnpm/action-setupwithcorepack enable, which respects the action's ownpackageManagerfield.2. Missing
v0tag due to release workflow mismatchProblem:
tempoxyz/lints@v0release-tags.ymlexpects tags matching^v([0-9]+)\.([0-9]+)\.([0-9]+)$to create major version tagschangeset tagcreates tags like@tempoxyz/lints@0.1.1v0was never createdFix:
release.ymlto create avX.Y.Ztag from the changeset tag before creating the GitHub releaserelease-tags.ymlto properly create/update the major version tag (v0)Manual tag creation
I also pushed
v0.1.1andv0tags manually to fix the existing release:v0.1.1points to the same commit as@tempoxyz/lints@0.1.1v0points tov0.1.1Test plan
tempoxyz/lints@v0now resolves correctly in GitHub Actions