chore(release): 1.3.0 - #52
Merged
Merged
Conversation
Closes #29. Mirrors Python 3.11 PEP 678 (BaseException.add_note()). Was documented but never implemented; consumers got a TypeScript error when following the JSDoc examples. The notes: string[] storage was already wired up; only the method was missing. - types.ts: declare addNote(note: string): ErrorInstance<TFields>; drop the stale 'TODO: Implement .addNote()' comment and the 'implemented in a separate task' notice. - error.ts: implement addNote in the factory closure. Pushes to notes and returns this for chaining. - tests/error.test.ts: cover single note, chained notes, preservation through .from(), and isolation between siblings. Adds a changeset (minor bump) for the new API.
…stacked-PR learnings Three process docs under docs/internal/engineering/process/, each tuned to a persona: - implementing-an-issue.md — dev's playbook (read issue, branch, code, changesets, push, PR). Companion for anyone picking up an issue. - releasing-a-new-version.md — release engineer's playbook (build the release branch, cherry-pick, push, watch the workflow, verify artifacts). Mirrors the conventions we hardened in PRs #39-47. - pr-authoring.md — standards for the body of a PR (six canonical sections, mandatory code sample when public API changes, before/after default, after-only when purely additive). Enforces what PR #50 demonstrated: documented the .addNote() worked-example as the in-doc template. Also adds docs/learnings/github/stacked-pr/README.md, notes captured during PR #39-43 setup around how stacked PRs work in GitHub and how they apply to a release branch. No code, no workflow changes. Documentation only.
- Prettier auto-formatted two of the four process docs (markdown table alignment in pr-authoring.md, bullet spacing in implementing-an-issue.md). - Add a no-op changeset so the ci.yml lint passes. The lint currently requires a changeset on every PR to staging regardless of path; this is a known limitation tracked in the release-system plan Section 4. A future change can implement the documented exemption for docs-only and CI-only PRs.
Bump @deessejs/errors to 1.3.0.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
martyy-code
force-pushed
the
release/1.3.0
branch
from
August 4, 2026 08:24
490b645 to
e4ea2ad
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
2 participants
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.
Release 1.3.0 of @deessejs/errors.