mcp/carbon-components-svelte
1
0
Fork 0
mirror of https://github.com/carbon-design-system/carbon-components-svelte.git synced 2025-09-14 18:01:06 +00:00
Code Issues Projects Releases Packages Wiki Activity

docs: update CONTRIBUTING.md (#1842)

Browse source
This commit is contained in:
metonym 2023-11-12 14:25:37 -08:00 • committed by GitHub
commit 0fdb9aa9e2
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 33 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

47
CONTRIBUTING.md
View file

@ -165,27 +165,44 @@ The following items only apply to project maintainers.
### Release ### Release
This library is published to NPM with [provenance](https://docs.npmjs.com/generating-provenance-statements) via a [GitHub workflow](https://github.com/carbon-design-system/carbon-components-svelte/blob/master/.github/workflows/release.yml).
The workflow is automatically triggered when pushing a tag that begins with `v` (e.g., `v0.81.1`).
However, maintainers must perform a few things in preparation for a release.
Locally, while on `master` and the branch is clean, run `yarn release`. This command will: Locally, while on `master` and the branch is clean, run `yarn release`. This command will:
- Build library and docs - Bump the semantic version in `package.json`
- Bump package.json version - Generate notes in `CHANGELOG.md`
- Add notes to Changelog - Run `yarn build:docs` to update the generated documentation
This command will not create a commit nor tag. Afterwards, perform the following manually: This command will not create a commit nor tag. Afterwards, perform the following manually:
```sh ```sh
# 1. Stage prepared files for a commit # 1. Commit the changes using the new version as the commit message.
git add . git commit -am "v0.81.1"
# 2. Commit based on the current version, either manually or with jq # 2. Create a tag.
git commit -m "v$(jq -r '.version' package.json)" git tag v0.81.1
# 3. Create a tag based on the current version, either manually or with `jq`: # 3. Push the tag to the remote.
git tag "v$(jq -r '.version' package.json)" # This will trigger the `release.yml` workflow to publish a new package to NPM (with provenance).
git push origin v0.81.1
# 4. Push branch and tag, then publish ```
git push origin master [tag]
yarn publish If all goes as expected, the [`release.yml` workflow](https://github.com/carbon-design-system/carbon-components-svelte/actions/workflows/release.yml) should trigger a new run and publish the new version to NPM.
# 5. Generate release notes on GitHub, and comment on issues and pull requests ### Post-release checklist
After confirming that the new release is published to NPM, perform the following:
1. Create a [new release](https://github.com/carbon-design-system/carbon-components-svelte/releases/new) on GitHub. Click "Generate release notes" to automatically list changes by commit with the relevant Pull Request and author metadata. You may manually remove notes that are not relevant to the release (e.g., CI changes).
2. Publish the release as the latest release.
3. As good practice, visit the Pull Request and/or issue for each commit and manually confirm that it's been released. This is helpful for future readers to understand what version includes the new feature or fix.
```md
Released in [v0.81.1](https://github.com/carbon-design-system/carbon-components-svelte/releases/tag/v0.81.1).
``` ```

3
package.json
View file

@ -17,8 +17,7 @@
"build:docs": "node scripts/build-docs", "build:docs": "node scripts/build-docs",
"build:lib": "rollup -c", "build:lib": "rollup -c",
"format": "prettier --write \"./**/*.{svelte,js,md}\"", "format": "prettier --write \"./**/*.{svelte,js,md}\"",
"prepack": "yarn build:docs & yarn build:lib", "release": "standard-version && yarn build:docs"
"release": "standard-version && yarn prepack"
}, },
"dependencies": { "dependencies": {
"flatpickr": "4.6.9" "flatpickr": "4.6.9"