chore: release new version 🚀#658
Open
cameri wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
5 times, most recently
from
July 4, 2026 10:50
4ba75ee to
71ffce0
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
July 9, 2026 23:12
43f217f to
7df692f
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
6 times, most recently
from
July 20, 2026 11:27
cc635f3 to
bae0bd1
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
July 20, 2026 18:36
e8670ab to
ebe02d0
Compare
Releases: nostream@3.1.0 [skip ci]
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 22, 2026 01:08
ebe02d0 to
2dd35f9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
nostream@3.1.0
Minor Changes
#641
837540bThanks @Ferryx349! - feat: add disabled-by-default admin API with password auth, session, and health endpoints#666
44f3bb4Thanks @Ferryx349! - feat: add admin observability dashboard with Grafana embed and provisioned metrics panels#653
8ab4825Thanks @Ferryx349! - feat: add OpenTelemetry metrics bootstrap with OTLP export for Prometheus#661
237b1a4Thanks @Ferryx349! - feat: instrument event and websocket handlers with OpenTelemetry metrics#662
36d95ccThanks @Ferryx349! - feat: add Prometheus-backed admin metrics SSE endpoint#587
30fa252Thanks @Anshumancanrock! - Add NIP-50 full-text search support with PostgreSQLtsvector/GINindexing.Clients can now include a
searchfield in REQ filter objects to perform full-textqueries against event content. Results are ranked by relevance (
ts_rank) insteadof the usual
created_atordering, per the NIP-50 specification.Features:
searchfilter field accepted in REQ messagesto_tsvector('simple', event_content)for fast full-text lookupssimple, supportsenglish,spanish, etc.)#702
e172cceThanks @Anshumancanrock! - feat(nip42): enforce authentication on reads for restricted event kinds (encrypted DMs, gift wraps) across REQ, live broadcasts and COUNT#650
3461dfeThanks @Anshumancanrock! - Add NIP-43 invite code foundation: InviteCodeRepository with atomic claimCode, invite_codes migration, and event kind/tag constants.#676
0bfa0b5Thanks @Anshumancanrock! - Add NIP-43 join/leave request event strategies (kinds 28934/28936) with NIP-42 auth enforcement, created_at freshness validation, invite code claiming, and admission management. Whennip43.enabledis set, publishing is restricted to admitted members even without payments enabled, and NIP-43 is advertised in the NIP-11 document (hidden when disabled). Join/leave update the admission cache so membership changes take effect immediately.#644
2f6d773Thanks @Anshumancanrock! - feat: reject NIP-70 protected events and reposts embedding them#672
595c0a6Thanks @Ferryx349! - refactor: extract shared settings-config module and guided schema for admin settings editor foundationPatch Changes
#646
eb64d8aThanks @dependabot! - chore(deps): bump js-yaml from 4.1.1 to 4.2.0#694
7c4b728Thanks @Priyanshubhartistm! - fix: de-duplicate events returned by generic tag-filter subscriptionsEventRepository.findByFilters()left-joinsevent_tagsfor generic tag filters(
#e,#p, etc.) without deduplicating the result. An event matching more than onetag row for the same filter (e.g.
{"#p": ["a", "b"]}matching an event tagged withboth) was returned once per matching
event_tagsrow, so subscribers received thesame
EVENTmessage multiple times. The query now selectsDISTINCT events.*fortag-filtered queries so each stored event is returned at most once. This also covers
generic tag filters combined with a NIP-50
searchterm (e.g.{"search": "...", "#p": ["a", "b"]}), which take the search branch and are nowde-duplicated as well.
#640
ca23be1Thanks @Anshumancanrock! - test: optimize nip05.spec.ts & nip03.spec.ts resource managementbefore/afterin verifyNip05Identifier tests (create once, reset between tests)beforeinstead of per-testbeforeEach#686
cb7daf6Thanks @Priyanshubhartistm! - fix: stop checking additional rate limit windows once a client is already rate-limitedisRateLimited()inEventMessageHandlerandWebSocketAdapterlooped through everyconfigured rate limit window even after one had already tripped, calling
rateLimiter.hit()(a Redis write) for each remaining window. Both now return as soon as the first exceeded
window is found, avoiding redundant Redis writes for clients that are already being limited.
#684
3648954Thanks @Priyanshubhartistm! - fix: await Redis EXISTS call in RedisAdapter.hasKey() so it reflects actual key presence instead of always returning true#682
dc78df5Thanks @Priyanshubhartistm! - fix: prevent crash in NIP-11 relay information document when payments settings are absent