chore: add release:v3 script and update workflow for 3.x branch - SFS-3144#3286
chore: add release:v3 script and update workflow for 3.x branch - SFS-3144#3286eduardoformiga merged 2 commits intodevfrom
Conversation
- Added a new script "release:v3" in package.json for versioning and publishing with a dist-tag of v3-latest. - Updated GitHub Actions workflow to include a new job for publishing on the 3.x branch.
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (2)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
- Added a condition to the Chromatic publishing step to skip execution on the 3.x branch, ensuring that releases are managed appropriately across different branches.
@faststore/api
@faststore/cli
@faststore/components
@faststore/core
@faststore/graphql-utils
@faststore/lighthouse
@faststore/sdk
@faststore/ui
commit: |
What's the purpose of this pull request?
release.yml3.xadicionado ao trigger de branchesPublish (3.x)com condiçãoif: github.ref_name == '3.x'apontando parapnpm release:v3package.jsonrelease:v3comlerna version --conventional-commits --yes && lerna publish from-git --dist-tag=v3-latest --yes--conventional-graduate(correto, pois no3.xnão haverá prereleases para graduar)--conventional-prerelease(correto, pois serão releases estáveis da v3)--dist-tag=v3-latest(correto, para não sobrescrever a taglatestque será da v4)Os hotfixes da v3 publicados a partir do branch
3.xserão instaláveis vianpm install @faststore/core@v3-lateste não vão interferir com a taglatestda v4.Nota importante: não usem pnpm release (o mesmo da main) no branch 3.x, porque esse comando usa --conventional-graduate que é para graduar prereleases. No 3.x, hotfixes serão commits normais (fix:, feat:) e o lerna version --conventional-commits (sem graduate) é o adequado — ele vai gerar 3.99.1, 3.99.2, etc., baseado nos commits.