chore: align changesets scripts, docs, and PR checklist

Author: Justxd22

.changeset/unreleased-since-v2.1.0.md

@@ -2,7 +2,7 @@
 "nostream": minor
 ---
 
-Unreleased changes since v2.1.0:
+Release highlights:
 
 **Features**
 - NIP-05 verification support (#463)
@@ -14,6 +14,7 @@ Unreleased changes since v2.1.0:
 - Opt-in event retention purge (#359, #412)
 - Wipe events table script (#450)
 - Nginx reverse proxy in docker-compose (#423)
+- Docker DNS pre-flight check for connectivity verification (#398)
 - Strict validation for payment callbacks (#426)
 - Real home page with templated pages (#409)
 
@@ -24,6 +25,7 @@ Unreleased changes since v2.1.0:
 - NIP-11 served only on root path instead of relay path (#399)
 - Dockerfile: run database migrations in CMD (#422)
 - Added expired_at filter to message pipeline (#403)
+- Removed unsafe-inline and implemented script nonces for CSP hardening (#394)
 - Axios upgraded to fix CVE-2025-62718 (#466)
 
 **Refactors & Chores**

.github/PULL_REQUEST_TEMPLATE.md

@@ -33,4 +33,5 @@
 - [ ] I have updated the documentation accordingly.
 - [ ] I have read the **CONTRIBUTING** document.
 - [ ] I have added tests to cover my code changes.
+- [ ] I added a changeset, or this is docs-only and I added an empty changeset.
 - [ ] All new and existing tests passed.

.github/workflows/changesets.yml

@@ -29,8 +29,8 @@ jobs:
       - name: Create Release Pull Request or Publish
         uses: changesets/action@v1
         with:
-          version: npm run version
-          publish: npm run publish
+          version: npm run changeset:version
+          publish: npm run changeset:tag
           createGithubReleases: true
         env:
           GITHUB_TOKEN: ${{ secrets.RELEASE_PAT }}

CONTRIBUTING.md

@@ -20,11 +20,47 @@ npm run knip
 
 1. Update the relevant documentation with details of changes to the interface, this includes new environment
    variables, exposed ports, useful file locations and container parameters.
-2. Increase the version numbers in any examples files and the README.md to the new version that this
-   Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
+2. Follow the versioning and changeset process described in [Releases & Versioning](#releases--versioning).
 3. You may merge the Pull Request in once you have the sign-off of two other developers, or if you
    do not have permission to do that, you may request the second reviewer to merge it for you.
 
+## Releases & Versioning
+
+This project uses [Changesets](https://github.com/changesets/changesets) for version management.
+
+### For contributors
+
+Every pull request that changes behavior, adds a feature, or fixes a bug **must include a changeset file**. The CI `changeset-check` job will fail if no changeset is present.
+
+To add a changeset:
+
+```bash
+npx changeset
+```
+
+This interactive prompt will ask you to:
+1. Select the bump type: `major`, `minor`, or `patch`
+2. Write a short summary of the change (this becomes the changelog entry)
+
+The command creates a file in `.changeset/` — commit it with your PR.
+
+### Docs-only PRs (no release)
+
+If your PR only updates documentation and should not affect versioning, add an empty changeset:
+
+```bash
+npx changeset --empty
+```
+
+Commit the generated `.changeset/*.md` file with your PR. This satisfies CI without producing a version bump or changelog entry.
+
+### Release process
+
+1. Changesets accumulate as PRs are merged to `main`
+2. The `Changesets Release` workflow automatically opens a **"Version Packages"** PR that aggregates all pending changesets, bumps `package.json`, and updates `CHANGELOG.md`
+3. When a maintainer merges the Version Packages PR, the workflow publishes a GitHub release and creates the corresponding git tag
+4. The Docker image is then automatically built and pushed to GHCR via the `release.yml` workflow
+
 ## Code Quality
 
 Run Biome checks before opening a pull request:

README.md

@@ -639,33 +639,6 @@ Any changes made to the settings file will be read on the next start.
 Default settings can be found under `resources/default-settings.yaml`. Feel free to copy it to `nostream/.nostr/settings.yaml` if you would like to have a settings file before running the relay first.
 
 See [CONFIGURATION.md](CONFIGURATION.md) for a detailed explanation of each environment variable and setting.
-## Releases & Versioning
-
-This project uses [Changesets](https://github.com/changesets/changesets) for version management.
-
-### For contributors
-
-Every pull request that changes behavior, adds a feature, or fixes a bug **must include a changeset file**. The CI `changeset-check` job will fail if no changeset is present.
-
-To add a changeset:
-
-```bash
-npx changeset
-```
-
-This interactive prompt will ask you to:
-1. Select the bump type: `major`, `minor`, or `patch`
-2. Write a short summary of the change (this becomes the changelog entry)
-
-The command creates a file in `.changeset/` — commit it with your PR.
-
-### Release process
-
-1. Changesets accumulate as PRs are merged to `main`
-2. The `Changesets Release` workflow automatically opens a **"Version Packages"** PR that aggregates all pending changesets, bumps `package.json`, and updates `CHANGELOG.md`
-3. When a maintainer merges the Version Packages PR, the workflow publishes a GitHub release and creates the corresponding git tag
-4. The Docker image is then automatically built and pushed to GHCR via the `release.yml` workflow
-
 ## Dev Channel
 
 For development discussions, please use the [Nostr Typescript Relay Dev Group](https://t.me/nostream_dev).

package.json

@@ -62,8 +62,8 @@
     "docker:cover:integration": "npm run docker:integration:run -- npm run cover:integration",
     "postdocker:integration:run": "docker compose -f ./test/integration/docker-compose.yml down",
     "prepare": "husky install || exit 0",
-    "version": "changeset version",
-    "publish": "changeset tag"
+    "changeset:version": "changeset version",
+    "changeset:tag": "changeset tag"
   },
   "repository": {
     "type": "git",