rel: prep v0.12.0

honeycombio · Oct 16, 2024 · cc450b7 · cc450b7
1 parent 1f6b162
commit cc450b7
Show file tree

Hide file tree

Showing 2 changed files with 36 additions and 3 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,5 +1,18 @@
 # buildevents-orb changelog
 
+## [0.12.0] - 2024-10-17
+
+### Enhancements
+
+- feat(w3c): partially implement w3c tracecontext (#110) | [Liz Fong-Jones](https://github.com/lizthegrey)
+
+### Maintenance
+
+- maint(deps): upgrade buildevents binary (#111) | [Liz Fong-Jones](https://github.com/lizthegrey)
+- docs: update vulnerability reporting process (#109) | [Robb Kidd](https://github.com/robbkidd)
+- maint: update repo for pipeline team ownership (#108) | [Jamie Danielson](https://github.com/JamieDanielson)
+- change codeowners to pipeline (#107) | [Brooke Sargent](https://github.com/brookesargent)
+
 ## [0.11.1] - 2024-03-19
 
 ### Fixed

diff --git a/RELEASING.md b/RELEASING.md
@@ -1,8 +1,28 @@
 # Releasing
 
-- Update `CHANGELOG.md` with the changes since the last release. Consider automating with a command such as these two:
-  - `git log $(git describe --tags --abbrev=0)..HEAD --no-merges --oneline > new-in-this-release.log`
-  - `git log --pretty='%C(green)%d%Creset- %s | [%an](https://github.com/)'`
+- Update `CHANGELOG.md` with the changes since the last release.
+  - Use below command to get a list of all commits since last release
+
+    ```sh
+    git log <last-release-tag>..HEAD --pretty='%Creset- %s | [%an](https://github.com/%an)'
+    ```
+
+  - Copy the output from the command above into the top of [changelog](./CHANGELOG.md)
+  - fix each `https://github.com/<author-name>` to point to the correct github username
+  (the `git log` command can't do this automatically)
+  - organize each commit based on their prefix into below three categories:
+
+    ```sh
+    ### Features
+      - <a-commit-with-feat-prefix>
+
+    ### Fixes
+      - <a-commit-with-fix-prefix>
+
+    ### Maintenance
+      - <a-commit-with-maintenance-prefix>
+    ```
+
 - 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 (e.g. `git tag -a v2.3.1 -m "v2.3.1"`)