@daften/fireflyiii-mcp 0.4.5 → 0.4.7-nightly.20260912T0736

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 +24 -1
  2. package/package.json +5 -5
package/CHANGELOG.md CHANGED
@@ -7,6 +7,28 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ### Fixed
11
+
12
+ - Match Dependabot security alerts using both bare and equals-prefixed versions, check all grouped dependencies and alert pages, and distinguish API failures from unmatched advisories.
13
+ - Distinguish back-merge conflicts from other Git failures and retry rejected pushes only when `develop` actually moved. Allow manually retrying the back-merge workflow.
14
+
15
+ ### Changed
16
+ - 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.
17
+ - `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.
18
+ ## [0.4.6] - 2026-09-11
19
+
20
+ ### Security
21
+
22
+ - chore(deps): update Vitest to patched 4.1.11 and fix CI install retries (automated security release)
23
+
24
+ ### Security
25
+
26
+ - Update Vitest and its coverage plugin to 4.1.11 to pick up the patched mocker while retaining Node 20 support.
27
+
28
+ ### Fixed
29
+
30
+ - Fail CI and nightly dependency installation when all retries fail, instead of continuing without the required tools.
31
+
10
32
  ## [0.4.5] - 2026-09-11
11
33
 
12
34
  ### Security
@@ -165,7 +187,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
165
187
  - npm publish provenance via GitHub OIDC.
166
188
  - GitHub Release auto-created from the tag annotation on each `v*` tag push.
167
189
 
168
- [Unreleased]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.5...HEAD
190
+ [Unreleased]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.6...HEAD
191
+ [0.4.6]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.5...v0.4.6
169
192
  [0.4.5]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.4...v0.4.5
170
193
  [0.4.4]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.3...v0.4.4
171
194
  [0.4.3]: https://github.com/daften/fireflyiii-mcp/compare/v0.4.2...v0.4.3
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@daften/fireflyiii-mcp",
3
- "version": "0.4.5",
3
+ "version": "0.4.7-nightly.20260912T0736",
4
4
  "description": "MCP server for Firefly III personal finance manager",
5
5
  "type": "module",
6
6
  "bin": {
@@ -61,15 +61,15 @@
61
61
  "hono": "^4.13.7"
62
62
  },
63
63
  "devDependencies": {
64
- "@biomejs/biome": "2.5.6",
64
+ "@biomejs/biome": "2.5.11",
65
65
  "@types/node": "^26.0.0",
66
- "@vitest/coverage-v8": "^4.1.8",
66
+ "@vitest/coverage-v8": "^4.1.11",
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.18",
72
- "vitest": "^4.1.7"
71
+ "vitepress": "2.0.0-alpha.19",
72
+ "vitest": "^4.1.11"
73
73
  },
74
74
  "engines": {
75
75
  "node": ">=20"