Vlad Durnea
cffdf8af86
Some checks failed
CI/CD Pipeline / unit-tests (push) Failing after 1m16s
CI/CD Pipeline / integration-tests (push) Failing after 2m32s
CI/CD Pipeline / lint (push) Successful in 5m22s
CI/CD Pipeline / e2e-tests (push) Has been skipped
CI/CD Pipeline / build (push) Has been skipped
20 lines
1011 B
Markdown
20 lines
1011 B
Markdown
# Releasing date-fns
|
|
|
|
1. First, make sure that the library is built by running `./scripts/build/build.sh` and committing and pushing any change you would have.
|
|
|
|
2. Then add the changelog entry generated by `npx tsx scripts/release/buildChangelog.ts` to (CHANGELOG.md)[../CHANGELOG.md]. Make sure that the output is valid Markdown and fix if there're any errors. Commit and push the file.
|
|
|
|
3. Using the version that the changelog script generated, run the command:
|
|
|
|
```bash
|
|
env VERSION="vX.XX.X" APP_ENV="production" GOOGLE_APPLICATION_CREDENTIALS="secrets/production/key.json" ./scripts/release/release.sh
|
|
```
|
|
|
|
The script will change `package.json`. **Do not commit the change, and reset it instead**.
|
|
|
|
4. Now when the package is published, go to [GitHub Releases](https://github.com/date-fns/date-fns/releases) and draft a new version using the changelog entry you generated earlier.
|
|
|
|
5. Finally, write an announce tweet using the created GitHub release as the tweet link.
|
|
|
|
You're done, great job!
|