chore(release): 1.0.3

[msalvatti]

Cuts 1.0.3. No runtime change — dist/ is byte-identical to 1.0.2, and I verified that rather than assumed it: unpacked the published tarball from the registry and diffed it against a fresh build.

What the 1.0.3 tarball will contain, relative to 1.0.2:

Entry
dist/	byte-identical — not one byte of runtime changed
LICENSE	identical
README.md	the reason for this release (below)
CHANGELOG.md	gains the 1.0.3 entry
package.json	version bumped to 1.0.3

src/ has not been touched since v1.0.2. The two PRs that landed in between (#57, #58) changed test/, .github/ and docs/, none of which enter the tarball — so everything that differs is either documentation or the version string itself.

Why release at all, then

The published README carries a dead link. Its "Example App" pointed at github.com/bymaxone/nest-queue/tree/main/examples/nest-queue-example — a directory #57 renamed to test/consumer-app. Confirmed HTTP 404.

That link matters most exactly where we are least likely to notice it: the package page on npmjs.com, read by people who have never seen this repository.

It now points at bymaxone/nest-queue-example — verified HTTP 200 anonymously, which is the check that counts, since the reader is not logged into our org.

Worth recording: this release was deliberately held until that repository was made public. Publishing earlier would have swapped one 404 for another, which is motion rather than a fix.

The README also no longer lets the two artifacts blur together — the reference application is where you copy from, test/consumer-app is a compile-time gate that is not published and not a demo.

Why a patch

There is no feature, so a minor would be a false signal. A patch is the honest label for a documentation correction.

Release-notes wiring

release.yml extracts the section matching the pushed tag. Simulated it against this file with the workflow's own awk:

$ awk -v ver="1.0.3" '…' CHANGELOG.md   →   30 lines, the full entry

The heading uses an em dash (## [1.0.3] — 2026-08-01), matching all three existing entries in this file. (The sibling libraries use a hyphen; this repository does not, and I left its convention alone.)

Gate

typecheck · test:types · lint · 276 tests at 100% (567/567 statements, 231/231 branches) · build · size · check:exports (attw, no problems) · dogfood smoke.

---

After merge, git tag v1.0.3 && git push --tags publishes with SLSA provenance. Ready for your review — not merging it.

[Copilot]

Pull request overview

Cuts release v1.0.3 for @bymax-one/nest-queue, intended as a documentation-only publish with no runtime (dist/) changes.

Changes:

• Bump package version from 1.0.2 → 1.0.3.
• Add a 1.0.3 changelog entry documenting the README “Example App” link correction and clarifying the role of test/consumer-app.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
package.json	Version bump to 1.0.3 for the release.
CHANGELOG.md	Adds the 1.0.3 release notes describing the documentation-only change.