chore: release package(s) #1
Open
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
changesets-gitlab@0.13.0
Minor Changes
e9adb24
Thanks @JounQin! - chore: housekeeping, bump all (dev) deps, addmodule-sync
entryfix:
commonjs
types entry#195
e7cbdff
Thanks @WeslleyNasRocha! - feat: fetch the tags and push each one individually based on size ofpackages
to be published andapi.FeatureFlags(projectId, 'git_push_create_all_pipelines')
#209
4ca179c
Thanks @JounQin! - feat: add a new optionalGITLAB_COMMENT_CUSTOM_LINKS
environment variable to override the links content referenced in the cli bot comment, use{{ addChangesetUrl }}
placeholder for the dynamic URL to add a changeset#196
b681513
Thanks @crysadrak! - feat: add a new optionalGITLAB_COMMENT_DISCUSSION_AUTO_RESOLVE
environment variable to automatically resolve added discussion when changeset is present, if you want to always resolve the discussion, you should actually useGITLAB_COMMENT_TYPE=note
instead, defaulttrue
efc0650
Thanks @JounQin! - refactor: publish releases with limited concurrency withp-limit