Skip to content

Release v4.6.0 - #518

Merged
janpaepke merged 5 commits into
masterfrom
chore/release-4-6-0
Jun 30, 2026
Merged

Release v4.6.0#518
janpaepke merged 5 commits into
masterfrom
chore/release-4-6-0

Conversation

@janpaepke

Copy link
Copy Markdown
Collaborator

Summary

Prepares the v4.6.0 release. Full flat list in CHANGELOG.md; categorized notes for the GitHub Release body are drafted in RELEASE_NOTES_v4.6.0.md.

New APIs

Runtime & compatibility

Enhancements

Type & documentation sync

Fixes

Deprecations

Maintenance

Release prep (this PR)

  • Update changelog, add missing @since 4.6.0 tags, deprecate the numeric profiles categoryCode, clarify the release-process docs, and bump to 4.6.0.

Aggregate the user-facing changes merged since v4.5.0, ordered by significance (new APIs, enhancements, type/docs sync, fixes, deprecations, maintenance). Internal-only changes (test refactors, the maintainer skill) are intentionally excluded.
Both helper accessors are new in this cycle but shipped without the @SInCE tag every other 4.6.0 addition carries; add it for consistency.
…nessCategory

Profiles gained the string businessCategory this cycle, and onboarding already deprecates its numeric categoryCode. Annotate the profiles field consistently; the @deprecated propagates to the request params via PickOptional. JSDoc-only, non-breaking.
…fter approval)

master is protected, so the version bump rides in via a release PR rather than a direct push; verification must happen before npm version (the publish workflow only runs unit tests); and the tag should be pushed only once the PR is approved, to avoid stale-tag rework. Align CONTRIBUTING.md, the project CLAUDE.md, and the publish workflow header comment.
@janpaepke
janpaepke requested a review from edorivai June 30, 2026 14:25
@janpaepke janpaepke added this to the 4.6.0 milestone Jun 30, 2026

@edorivai edorivai left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed as a release PR. LGTM.

  • Version: 4.5.0 → 4.6.0 minor bump — correct, since the whole batch is additive + deprecations with no breaking changes.
  • CHANGELOG: cross-checked against every PR merged since v4.5.0 — complete and accurate. Correctly omits the non-user-facing ones (#481 test fix, #493 test reorg, #513 dev tooling). Date is today.
  • src changes: three @since 4.6.0/@deprecated JSDoc backfills (InvoiceHelper.getPdfUrl, OrganizationHelper.getDashboardUrl, profile categoryCode→businessCategory) — appropriate; other new helpers already carried @since from their own PRs.
  • Process docs (CLAUDE.md/publish.yml/CONTRIBUTING.md) now match the protected-master / release-PR flow this PR uses. Self-consistent.

One pre-publish check (not blocking this PR): #508 (terminal pairing codes) ships in this release and was previously held over two unverified runtime constants — the resource dispatch string (terminal-pairing-code) and the _embedded key (terminal-pairing-codes). Worth confirming both against a real API response before publishing the GitHub Release, since a wrong value throws at runtime on every pairing-code call.

@janpaepke
janpaepke merged commit bddef14 into master Jun 30, 2026
12 checks passed
@janpaepke
janpaepke deleted the chore/release-4-6-0 branch June 30, 2026 14:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants