@daften/fireflyiii-mcp 0.4.3-nightly.20260830T0850 → 0.4.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/CHANGELOG.md +17 -4
  2. package/package.json +3 -3
package/CHANGELOG.md CHANGED
@@ -7,9 +7,20 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
- ### Changed
11
- - Releases are now cut on a short-lived `release/X.Y.Z` branch that reaches `main` as a single PR, instead of a promotion merge followed by a separate release commit on `main`. Since `backmerge.yml` runs on every push to `main`, the old shape back-merged twice per release; this shape does it once, puts the release commit through CI, and leaves `auto-release.yml` as the only thing committing directly to `main`. `backmerge.yml` itself now merges and pushes to `develop` directly, opening a PR only when the merge conflicts and needs manual resolution.
12
- - `CHANGELOG.md` now has a `merge=union` driver (`.gitattributes`), so `develop`'s pending `[Unreleased]` entries and `main`'s freshly-cut dated release sections no longer conflict on every back-merge — git keeps both sides automatically instead of failing.
10
+ ## [0.4.4] - 2026-09-05
11
+
12
+ ### Security
13
+
14
+ - chore(deps): Bump qs from 6.15.2 to 6.16.0 in the security-fixes group across 1 directory (automated security release)
15
+
16
+ ### Fixed
17
+ - `auto-merge.yml` still never enabled auto-merge on Dependabot security PRs. `alert-lookup` was being passed the default `GITHUB_TOKEN`, which cannot read the Dependabot alerts API; `dependabot/fetch-metadata` reports that by returning an empty `alert-state` instead of failing, so the merge step's guard stayed false while the job reported success. The metadata step now uses the `RELEASE_TOKEN` PAT (which needs `Dependabot alerts: Read only`), and a new guard step fails the job outright when a `security-fixes`-group PR produces no `alert-state`, so an expired or under-scoped token can no longer masquerade as a passing check. ([#86](https://github.com/daften/fireflyiii-mcp/pull/86))
18
+
19
+ ## [0.4.3] - 2026-09-03
20
+
21
+ ### Security
22
+
23
+ - chore(deps): Bump fast-uri from 3.1.5 to 3.1.7 in the security-fixes group across 1 directory (automated security release)
13
24
 
14
25
  ## [0.4.2] - 2026-08-04
15
26
 
@@ -148,7 +159,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
148
159
  - npm publish provenance via GitHub OIDC.
149
160
  - GitHub Release auto-created from the tag annotation on each `v*` tag push.
150
161
 
151
- [Unreleased]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.2...HEAD
162
+ [Unreleased]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.4...HEAD
163
+ [0.4.4]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.3...v0.4.4
164
+ [0.4.3]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.2...v0.4.3
152
165
  [0.4.2]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.1...v0.4.2
153
166
  [0.4.1]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.0...v0.4.1
154
167
  [0.4.0]: https://github.com/daften/fireflyiii-mcp/compare/v0.3.4...v0.4.0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@daften/fireflyiii-mcp",
3
- "version": "0.4.3-nightly.20260830T0850",
3
+ "version": "0.4.4",
4
4
  "description": "MCP server for Firefly III personal finance manager",
5
5
  "type": "module",
6
6
  "bin": {
@@ -61,14 +61,14 @@
61
61
  "hono": "^4.13.0"
62
62
  },
63
63
  "devDependencies": {
64
- "@biomejs/biome": "2.5.10",
64
+ "@biomejs/biome": "2.5.6",
65
65
  "@types/node": "^26.0.0",
66
66
  "@vitest/coverage-v8": "^4.1.8",
67
67
  "dotenv-cli": "^11.0.0",
68
68
  "simple-git-hooks": "^2.13.1",
69
69
  "tsx": "^4.22.3",
70
70
  "typescript": "^7.0.2",
71
- "vitepress": "2.0.0-alpha.19",
71
+ "vitepress": "2.0.0-alpha.18",
72
72
  "vitest": "^4.1.7"
73
73
  },
74
74
  "engines": {