Repository navigation
chore: release new version 🚀 - #827
Merged
Merged
Conversation
[Low impact] This release-only PR appears safe to merge.
|
Collaborator
Coverage Report for CI Build 38791642553Coverage decreased (-0.006%) to 74.488%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats💛 - Coveralls |
cameri
force-pushed
the
changeset-release/main
branch
from
October 15, 2026 18:06
98c763d to
a0aa044
Compare
greptile-apps
Bot
dismissed
their stale review
October 15, 2026 18:06
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
cameri
force-pushed
the
changeset-release/main
branch
from
October 15, 2026 19:09
a0aa044 to
9ff10f1
Compare
cameri
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 15, 2026 19:53
412276a to
a542121
Compare
cameri
force-pushed
the
changeset-release/main
branch
from
October 15, 2026 20:15
a542121 to
aee25ea
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.5.0
Minor Changes
#823
82287d4Thanks @Ferryx349! - feat(website): add Astro marketing site with landing film, docs, changelog and community pagesAdds
website/site(nostream.dev) and updates the landing hero animation to sync NIP count and branding from the repo. Docs, changelog, version label and NIP list are read from the repository at build time.#830
f0bcdccThanks @Priyanshubhartistm! - feat(nip77): advertise NIP-77 in NIP-11 supported_nips while it is active and expose its settings in the admin console#818
7409006Thanks @Priyanshubhartistm! - feat(nip77): serve NEG-OPEN, NEG-MSG and NEG-CLOSE negentropy sync for the PostgreSQL event storenostream-website@1.1.0
Minor Changes
#828
bb28debThanks @chappie-daemon! - feat(website): version and deploy the marketing sitewebsite/sitejoins the pnpm workspace asnostream-website, so the marketing site is versioned and released through the same changesets flow as the relay. The site builds as a static bundle (docs and changelog render from the repository at build time — no SSR) and deploys to Cloudflare Workers with static assets at ema.tnsor.network through CI.The deploy is a Cloudflare Worker with static assets (
website/site/wrangler.jsonc), built and shipped by the newDeploy Websiteworkflow after a release PR merges tomain.Patch Changes
b2a997dThanks @chappie-daemon! - Bind ema.tnsor.network as a wrangler-declared custom domain so every deploy idempotently attaches it to the nostream-website worker.