rbrooks/BatteryStorageCalculator
Watch
1
0
Fork
You've already forked BatteryStorageCalculator
 0
Code Issues 38 Pull requests 3 Projects Releases Packages Wiki Activity Actions

Adopt semantic versioning and maintain a changelog #5

New issue
Closed
opened 2026-07-17 01:17:54 +00:00 by claude-bot · 2 comments
claude-bot commented 2026-07-17 01:17:54 +00:00
Contributor
Copy link

The repo has no git tags and both package.json files are pinned at 1.0.0 regardless of what shipped. There is no record of what changed between versions.

  • Add CHANGELOG.md in Keep a Changelog format.
  • Reconstruct the version history from the 38 existing commits (2026-05-08 through 2026-06-03), marking clearly that pre-1.0.0 versions are retroactive and were never tagged at the time.
  • Use semantic versioning going forward, with an Unreleased section.

Optional follow-up: apply retroactive annotated git tags so Forgejo releases line up with the changelog. Deliberately not done initially - tagging history after the fact is easy to get wrong and the changelog carries the same information.

The repo has no git tags and both `package.json` files are pinned at `1.0.0` regardless of what shipped. There is no record of what changed between versions. - Add `CHANGELOG.md` in Keep a Changelog format. - Reconstruct the version history from the 38 existing commits (2026-05-08 through 2026-06-03), marking clearly that pre-1.0.0 versions are retroactive and were never tagged at the time. - Use semantic versioning going forward, with an `Unreleased` section. Optional follow-up: apply retroactive annotated git tags so Forgejo releases line up with the changelog. Deliberately not done initially - tagging history after the fact is easy to get wrong and the changelog carries the same information.
claude-bot commented 2026-07-17 01:29:22 +00:00
Author
Contributor
Copy link

Added CHANGELOG.md in Keep a Changelog format, with history reconstructed from the 38 commits spanning 2026-05-08 to 2026-06-03:

Version Date Theme
0.1.0 2026-05-08 Initial calculator, rate comparison, Emporia CSV import
0.2.0 2026-05-09 Arbitrage across all five plans, solar, dispatch toggles
0.3.0 2026-05-14 Quotes, Solar tab, analytics, outage/reserve, weather
0.4.0 2026-05-21 Usage impact explorer, auth proxy, async worker
0.5.0 2026-05-22 Persistence, shared runtime, server calc API, caching, reports
0.6.0 2026-06-01 Per-circuit whole-home backup exclusion
1.0.0 2026-06-03 Performance and reliability hardening

The file states plainly at the top that pre-1.0.0 versions are a retroactive reading of the commit log and were never tagged at the time — they are not checkout-able.

Deliberately did not apply retroactive git tags. You picked reconstruction without tagging, and I'd agree: the changelog carries the same information without asserting a precision the history doesn't have. Easy to add later if you want Forgejo releases to line up.

Staged in the working tree; not yet committed.

Added `CHANGELOG.md` in Keep a Changelog format, with history reconstructed from the 38 commits spanning 2026-05-08 to 2026-06-03: | Version | Date | Theme | | --- | --- | --- | | 0.1.0 | 2026-05-08 | Initial calculator, rate comparison, Emporia CSV import | | 0.2.0 | 2026-05-09 | Arbitrage across all five plans, solar, dispatch toggles | | 0.3.0 | 2026-05-14 | Quotes, Solar tab, analytics, outage/reserve, weather | | 0.4.0 | 2026-05-21 | Usage impact explorer, auth proxy, async worker | | 0.5.0 | 2026-05-22 | Persistence, shared runtime, server calc API, caching, reports | | 0.6.0 | 2026-06-01 | Per-circuit whole-home backup exclusion | | 1.0.0 | 2026-06-03 | Performance and reliability hardening | The file states plainly at the top that pre-1.0.0 versions are a retroactive reading of the commit log and were never tagged at the time — they are not checkout-able. **Deliberately did not apply retroactive git tags.** You picked reconstruction without tagging, and I'd agree: the changelog carries the same information without asserting a precision the history doesn't have. Easy to add later if you want Forgejo releases to line up. Staged in the working tree; not yet committed.
claude-bot commented 2026-07-17 02:00:52 +00:00
Author
Contributor
Copy link

Done in #20, merged as a0d604b. CHANGELOG.md reconstructs 0.1.0 through 1.0.0 from git history, marked plainly as retroactive and untagged.

Updated again in #21 to record the battery degradation and adjusted-payback work under Unreleased, which had been missed.

Done in #20, merged as `a0d604b`. `CHANGELOG.md` reconstructs 0.1.0 through 1.0.0 from git history, marked plainly as retroactive and untagged. Updated again in #21 to record the battery degradation and adjusted-payback work under `Unreleased`, which had been missed.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
renovate/lock-file-maintenance
renovate/pg-8.x
renovate/lucide-monorepo
No results found.
Labels
Clear labels   
bug
Defect: incorrect behavior or output

  
decision
Open design decision that gates other work

  
docs
Documentation

  
enhancement
New feature or capability

  
integration
External data source integration

  
ops
Deployment, CI, tooling, observability

  
security
Security hardening: missing or misplaced control

  
tech-debt
Cleanup of legacy or superseded code

  
testing
Test coverage

No labels
bug
decision
docs
enhancement
integration
ops
security
tech-debt
testing
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rbrooks/BatteryStorageCalculator#5
No description provided.