Skip to content

chore(release): 2.4.2 - #561

Merged
tcheeric merged 4 commits into
mainfrom
develop
Oct 4, 2026
Merged

tcheeric merged 4 commits into
mainfrom
develop

Conversation

@tcheeric

@tcheeric tcheeric commented Oct 4, 2026

Copy link
Copy Markdown
Owner

Summary

Release 2.4.2: promotes develop to main.

Closes #559

Type of change

  • fix - Bug fix (non-breaking)
  • docs - Documentation only
  • chore - Build, CI, or tooling changes

What changed?

Everything from #560:

  • GenericEvent.update() keeps a created_at that is already set and only stamps the clock when it is unset (null or 0), so the id always matches the event's own created_at (NIP-01). New updateWithCurrentTime() for deliberate restamping.
  • MCP server how-to mentions the Lyrebird bot.
  • Version 2.4.2 across all modules, CHANGELOG updated.

Testing

Checklist

  • PR title follows conventional commits
  • Tests added/updated for new functionality
  • CHANGELOG.md updated

tcheeric and others added 4 commits October 4, 2026 13:18
update() restamped created_at with the clock before computing the id, so
callers that set created_at got an id for a different second, and NIP-59
randomised timestamps were replaced by the send time. NIP-01 derives the
id from the event's own fields, so update() now only stamps the clock
when created_at is unset (null or zero). Restamping on purpose is
available through the new updateWithCurrentTime().

Fixes #559
- nostr-java (all modules): 2.4.1 → 2.4.2 (patch) [maven]

Fixed: GenericEvent.update() overwrote a caller-set created_at, so ids
could be computed for a different second (#559).
Added: GenericEvent.updateWithCurrentTime(), and the Lyrebird mention in
the MCP server how-to.
fix(event): keep a preset created_at in GenericEvent.update() (2.4.2)
@tcheeric
tcheeric merged commit 9afdd3a into main Oct 4, 2026
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

GenericEvent.update() silently overwrites created_at, so callers that set it get a mismatched id

1 participant