Skip to content

Commit

Permalink
Prepare 4.0.0 release (#623)
Browse files Browse the repository at this point in the history
  • Loading branch information
emilyashley committed Sep 21, 2022
1 parent ff7a9b5 commit 9f38b3f
Show file tree
Hide file tree
Showing 5 changed files with 38 additions and 10 deletions.
25 changes: 25 additions & 0 deletions CHANGELOG.md
@@ -1,5 +1,30 @@
# beeline-nodejs changelog

## 4.0.0 [2022-09-20]

### !!! Breaking Changes !!!

- Drop Node v12, no longer security supported (#614) | [@emilyashley](https://github.com/emilyashley)

### Maintenance

- maint: add node 18 to CI matrix (#610) | [@vreynolds](https://github.com/vreynolds)
- maint: make sure ci uses node matrix (#607) | [@vreynolds](https://github.com/vreynolds)
- Bump jest from 28.1.3 to 29.0.3 (#622)
- Bump fastify from 3.29.2 to 4.6.0 (#621)
- Bump @opentelemetry/core from 1.6.0 to 1.7.0 (#620)
- Bump @typescript-eslint/eslint-plugin from 5.37.0 to 5.38.0 (#619)
- Bump @typescript-eslint/parser from 5.37.0 to 5.38.0 (#618)
- Bump @typescript-eslint/eslint-plugin from 5.30.0 to 5.31.0 (#609)
- Bump eslint from 8.14.0 to 8.20.0 (#604)
- Bump @typescript-eslint/eslint-plugin from 5.27.0 to 5.30.0 (#600)
- Bump typescript from 4.7.3 to 4.7.4 (#599)
- Bump typescript from 4.6.4 to 4.7.3 (#598)
- Bump @typescript-eslint/eslint-plugin from 5.22.0 to 5.27.0 (#596)
- Bump @opentelemetry/core from 1.2.0 to 1.3.0 (#595)
- Bump jest from 28.0.3 to 28.1.0 (#594)
- Bump @typescript-eslint/parser from 5.22.0 to 5.27.0 (#593)

## 3.4.0 [2022-05-04]

### Enhancements
Expand Down
7 changes: 5 additions & 2 deletions RELEASING.md
Expand Up @@ -11,5 +11,8 @@
- Update `CHANGELOG.md` with the changes since the last release.
- Commit changes, push, and open a release preparation pull request for review.
- Once the pull request is merged, fetch the updated `main` branch.
- Apply a tag for the new version on the merged commit: vX.Y.Z, for example v1.1.2.
- Push the new version tag up to the project repository to kick off build and artifact publishing to GitHub and the NPM registry.
- Apply a tag for the new version on the merged commit (e.g. `git tag -a v2.3.1 -m "v2.3.1"`)
- Push the tag upstream (this will kick off the release pipeline in CI) e.g. `git push origin v2.3.1`
- Copy change log entry for newest version into draft GitHub release created as part of CI publish steps.
- Make sure to "generate release notes" in github for full changelog notes and any new contributors
- Publish the github draft release and this will kick off publishing to GitHub and the NPM registry.
10 changes: 5 additions & 5 deletions examples/node-tracing/package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Expand Up @@ -6,7 +6,7 @@
"node": "16.17.0"
},
"license": "Apache-2.0",
"version": "3.4.0",
"version": "4.0.0",
"repository": {
"type": "git",
"url": "https://github.com/honeycombio/beeline-nodejs.git"
Expand Down

0 comments on commit 9f38b3f

Please sign in to comment.