luxfi/zapdb
1
0
Fork 0
mirror of https://github.com/luxfi/zapdb.git synced 2026-07-26 22:46:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: Update changelog (#2256)

Browse Source 
**Description**

Updated the changelog
This commit is contained in:
Matthew McNeely
2026-02-04 15:55:07 -05:00
committed by GitHub
parent 0c07dc6ca8
commit 54d730a87e
4 changed files with 21 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/workflows/ci-badger-bank-tests.yml
+1
View File
@@ -1,6 +1,7 @@
name: ci-badger-bank-tests
on:
workflow_dispatch: # allows manual trigger from GitHub
pull_request:
paths-ignore:
- "**.md"
.github/workflows/ci-badger-tests.yml
+1
View File
@@ -1,6 +1,7 @@
name: ci-badger-tests
on:
workflow_dispatch: # allows manual trigger from GitHub
pull_request:
paths-ignore:
- "**.md"
CHANGELOG.md
+17
View File
@@ -4,6 +4,23 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/).
## [4.9.1] - 2026-02-04
**Fixed**
- fix(aix): add aix directory synchronization support (#2115)
- fix: correct the comment on value size in skl.node (#2250)
**Tests**
- test: add checksum tests for package y (#2246)
**Chores**
- chore(ci): update arm runner label (#2248)
**Full Changelog**: https://github.com/dgraph-io/badger/compare/v4.9.0...v4.9.1
## [4.9.0] - 2025-12-15
**Fixed**
contrib/RELEASE.md
+2 -2
View File
@@ -5,7 +5,7 @@ This document outlines the steps needed to build and push a new release of Badge
1. Have a team member "at-the-ready" with github `writer` access (you'll need them to approve PRs).
1. Create a new branch (prepare-for-release-vXX.X.X, for instance).
1. Update dependencies in `go.mod` for Ristretto, if required.
1. Update the CHANGELOG.md. Sonnet 4.5 does a great job of doing this. Example prompt:
1. Update the CHANGELOG.md. Opus 4.5 does a great job of doing this. Example prompt:
`I'm releasing vXX.X.X off the main branch, add a new entry for this release. Conform to the`
`"Keep a Changelog" format, use past entries as a formatting guide. Run the trunk linter.`
1. Validate the version does not have storage incompatibilities with the previous version. If so,
@@ -34,7 +34,7 @@ This document outlines the steps needed to build and push a new release of Badge
1. Splash the "go index" cache to ensure that the latest release is available to the public with:
```sh
go list -m github.com/dgraph-io/badger@vX.X.X
go list -m github.com/dgraph-io/badger/v4@vX.X.X
```
1. If needed, create a new announcement thread in the