feat: publish parley-core remote/chat OAuth mode (first automated release)#4
Merged
Conversation
…ease) Core's OIDC / remote-auth module (src/auth/*, src/testing/fake-oidc) landed after core's initial 0.1.0 npm publish and was never republished, so @sharptrick/parley-core@0.1.0 on npm is missing it. Merging this cuts 0.2.0 across all packages in lockstep via the automated pipeline, bringing npm current and adding provenance. The seam interface is unchanged. Adds a root CHANGELOG.md; GitHub Releases remain the canonical generated log. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Cuts the first automated release (
0.2.0) and brings npm fully current.Why
A tarball-vs-build audit found that
@sharptrick/parley-core@0.1.0on npm is stale: core's OIDC / remote-auth module (src/auth/*,src/testing/fake-oidc) landed on2026-07-02, a day after core was first published to npm on2026-07-01, and core was never republished. The other 11 packages are byte-identical tomain; only core is behind.What merging this does
The
feat:title bumps all 12@sharptrick/parley-*packages to0.2.0in lockstep via the release pipeline, republishing from currentmain— so core finally ships its OAuth/remote code, this time with provenance. From here on, npm ==main== tagv0.2.0.The seam interface is unchanged; no consumer API is altered.
Change in this PR
CHANGELOG.md(hand-kept highlights; GitHub Releases remain the canonical auto-generated log). The release itself is driven by the PR title.After merge
Watch the Release workflow: it should create tag
v0.2.0+ a GitHub Release and publish all 12 at0.2.0. (Prereq already done: trusted publishers configured for all 12.)🤖 Generated with Claude Code