Skip to content

ci: announce published packages on Discord - #280

Merged
RedStar071 merged 4 commits into
mainfrom
claude/hopeful-lovelace-6j2r91
Nov 13, 2026
Merged

RedStar071 merged 4 commits into
mainfrom
claude/hopeful-lovelace-6j2r91

Conversation

@RedStar071

@RedStar071 RedStar071 commented Nov 7, 2026 •

Copy link
Copy Markdown
Member

🔗 Linked issue

N/A

🧭 Context

Releases of @wolfstar/plugin-* packages are published with changesets, but nothing tells the community. This posts each release to Discord in the Sapphire announcement format, built from the changelogs, the same way as in stars-components.

The posting logic lives in the org wolfstar-project/.github repository as a reusable workflow (reusable-announce-packages.yml). This PR depends on it being merged there first. GitHub rejects a workflow file that calls a missing reusable workflow, so do not merge this before then.

📚 Description

After changesets/action publishes, a new announce job calls reusable-announce-packages.yml. For each published package it reads the matching CHANGELOG.md section and the PR titles, and posts # @wolfstar/plugin-api@3.1.0 - (date) followed by 💥 / 🚀 / 🐛 / 🏠 / 📦 sections, with links to the commit and the PR. No AI is involved. A failed announcement does not affect the release job, because the packages are already out: the announce job is separate and runs after the publish.

announce.yml is a manual workflow that re-sends or previews an announcement from a name@version list (dry-run defaults to on). The published-packages input takes either that list or the JSON array changesets/action outputs.

Optional signed lifecycle callbacks (X-Release-Signature-256) are off unless both RELEASE_WEBHOOK_URL and RELEASE_WEBHOOK_SECRET are set.

Key changes

  • release.yml: the release job exposes published and publishedPackages; new announce job. The old inline step that called a stars-components action is gone.
  • announce.yml (new): manual re-send or preview.
  • .github/zizmor.yml: wolfstar-project/.github/* may follow main (ref-pin); everything else stays hash-pinned.
  • AGENTS.md: documents the flow.
  • Empty changeset, since no package changes.

To turn it on, set the secret DISCORD_PACKAGES_WEBHOOK_URL and the variable DISCORD_PACKAGES_ROLE_ID. With no webhook the job only renders the preview in its summary.

Type of Change

  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation change
  • Workflow / CI change

Pre-flight Checklist

  • I have read the Contributing Guidelines (if applicable)
  • My code follows the code style of this project
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have updated the documentation accordingly
  • I added a changeset with pnpm changeset (or pnpm changeset add --empty if no release is needed). See .changeset/README.md.

No tests here: the workflow has no code of its own, and the action's tests (24) run in the .github repository. oxfmt is clean on the changed files. zizmor reports no finding on them; the one it still reports in pkg-pr-new.yml was already there.

🤖 AI disclosure: Claude Code was used on this PR. Code written with claude-opus-5-5 and claude-sonnet-5-5; PR description written with claude-sonnet-5-5. AI policy.

RetriggerView in GreptileConfidence Score: 4/5

Fix the Changesets output name before merging so automatic announcements receive the published packages.

Reviews (1) · Last reviewed commit: "Merge remote-tracking branch 'origin/mai..." · Reviewed by Greptile

Post each published package in the Sapphire format through the shared
announce action of stars-components, and add announce.yml to re-send or
preview an announcement by hand. zizmor allows that action to follow main.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016cicF4XnPH4SGMiXLz6nKh
release.yml and announce.yml call reusable-announce-packages.yml from
wolfstar-project/.github instead of the stars-components action.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016cicF4XnPH4SGMiXLz6nKh
No package changes: this only touches CI workflows.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016cicF4XnPH4SGMiXLz6nKh

Copy link
Copy Markdown
Member Author

The Security analysis (zizmor) check is red, and it is not caused by this PR.

  • What fails: two findings, both in files this PR does not touch: error[cache-poisoning] in pkg-pr-new.yml:31 and warning[ref-version-mismatch] in documentation.yml:20 (the hash pin there says # main, and the branch now points to another commit). Nothing in release.yml, announce.yml or zizmor.yml is reported.
  • Why it is not this PR's: the same check is red on main since the fix(deps): update all non-major dependencies (#272) merge (run 42239275748); the run before it was green.
  • Fix: none exists yet, and there is no open PR for it. The fix is a separate change: re-pin documentation.yml to the current main of the reusable workflow, and for pkg-pr-new.yml either drop cache: true from the step that publishes or add a documented ignore in .github/zizmor.yml. I left it out to keep this PR to the announce workflows.

This PR stays a draft until the shared workflows are merged in wolfstar-project/.github.


Generated by Claude Code

@wolfstar-github-agent

Copy link
Copy Markdown

🤖 REVIEW PAUSED

Wolfstar Agent Kit posted this automated status. AI open source policy.

This pull request is from an outside contributor.

Add the wolfstar-agent-review label to approve automated review and verified repairs.
Approval covers head commit 76878744cce8.

@RedStar071
RedStar071 marked this pull request as ready for review November 10, 2026 12:19
@coldtea-pr-lens

Copy link
Copy Markdown

Note

The title starts with ci:, so PR Lens left this pull request undrawn. Comment @pr-lens draw to draw it

github.comment.notice: false in .github/pr-lens.yml turns this note off

@pullfrog pullfrog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Important

The reusable workflow this PR calls does not exist yet, so merging now would break release.yml. Hold the merge until it lands.

Reviewed changes

Reviewed the full diff (5 files, 3 commits) against the current release.yml, and checked the wolfstar-project/.github repository for the called workflow.

  • release.yml: the release job now exposes published and publishedPackages, and a new announce job calls the shared reusable workflow.
  • announce.yml: new manual workflow to re-send or preview an announcement, with dry-run on by default.
  • .github/zizmor.yml: lets wolfstar-project/.github/* follow main (ref-pin) and keeps hash-pin for everything else.
  • AGENTS.md and changeset: documents the flow and adds an empty changeset.

⚠️ PR body carries a second attribution after the disclosure line

The body ends with the disclosure line followed by --- and _Generated by [Claude Code](https://claude.ai/code/session_…)_. AGENTS.md says the disclosure line is the only AI attribution a PR body may carry and that nothing may follow it, so that footer should be removed.

Technical details
# Remove the extra attribution footer from the PR body

## Affected sites
- PR #280 body — trailing `---` and `_Generated by [Claude Code](...)_` after the `🤖 AI disclosure` line

## Required outcome
- The body contains exactly one disclosure line and nothing after it.

Pullfrog  | Fix all ➔ | Fix 👍s ➔ | View workflow run | Using claude-sonnet-5-5 | 𝕏

Comment thread .github/workflows/release.yml Resolved
@RedStar071
RedStar071 marked this pull request as draft November 10, 2026 12:28
@pkg-pr-new

pkg-pr-new Bot commented Nov 12, 2026

Copy link
Copy Markdown

Open in StackBlitz

@wolfstar/plugin-api

pnpm add https://pkg.pr.new/@wolfstar/plugin-api@280

@wolfstar/plugin-broker

pnpm add https://pkg.pr.new/@wolfstar/plugin-broker@280

@wolfstar/plugin-cache

pnpm add https://pkg.pr.new/@wolfstar/plugin-cache@280

@wolfstar/plugin-gateway

pnpm add https://pkg.pr.new/@wolfstar/plugin-gateway@280

@wolfstar/plugin-i18next

pnpm add https://pkg.pr.new/@wolfstar/plugin-i18next@280

@wolfstar/plugin-logger

pnpm add https://pkg.pr.new/@wolfstar/plugin-logger@280

@wolfstar/plugin-opentelemetry

pnpm add https://pkg.pr.new/@wolfstar/plugin-opentelemetry@280

@wolfstar/plugin-scheduled-tasks

pnpm add https://pkg.pr.new/@wolfstar/plugin-scheduled-tasks@280

@wolfstar/plugin-sharder

pnpm add https://pkg.pr.new/@wolfstar/plugin-sharder@280

@wolfstar/plugin-subcommands-advanced

pnpm add https://pkg.pr.new/@wolfstar/plugin-subcommands-advanced@280

commit: 0bce45f

@RedStar071
RedStar071 marked this pull request as ready for review November 13, 2026 16:17
@pullfrog

pullfrog Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

This run was cancelled before it finished.

Pullfrog  | View workflow run | via Pullfrog

@RedStar071
RedStar071 merged commit 22f2836 into main Nov 13, 2026
14 of 17 checks passed
@RedStar071
RedStar071 deleted the claude/hopeful-lovelace-6j2r91 branch November 13, 2026 16:17
id-token: write
outputs:
published: ${{ steps.changesets.outputs.published }}
publishedPackages: ${{ steps.changesets.outputs.publishedPackages }}

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Published packages go unannounced

changesets/action v2 renamed its package-list output to published-packages, but this reads the old publishedPackages name. After a successful publish, announce runs with an empty package list and cannot announce the released packages. Read ${{ steps.changesets.outputs['published-packages'] }} here; the job output can still be named publishedPackages.

Suggested change
publishedPackages: ${{ steps.changesets.outputs.publishedPackages }}
publishedPackages: ${{ steps.changesets.outputs['published-packages'] }}
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/workflows/release.yml
Line: 108

Comment:
**Published packages go unannounced**

`changesets/action` v2 renamed its package-list output to `published-packages`, but this reads the old `publishedPackages` name. After a successful publish, `announce` runs with an empty package list and cannot announce the released packages. Read `${{ steps.changesets.outputs['published-packages'] }}` here; the job output can still be named `publishedPackages`.

```suggestion
      publishedPackages: ${{ steps.changesets.outputs['published-packages'] }}
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Fix in Claude Code Fix in Cursor

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