docs: release-notes house-style pass, flow doc, DM-the-notes on publish#14
Merged
Conversation
- publish-release-notes.yml: generate one customer <Update> entry from pasted release URLs (frontend/backend-aware, deduped, Opus 4.8 effort max), following AGENTS.md voice rules, then open a PR. The workflow never merges — main's ruleset requires an approving review, so your review and merge is the publish gate. - release-notes-published.yml: on merge to main, DM the published notes (Slack-formatted) so you can forward them to the prem-app channel. - release-notes.mdx: trim punchy em dashes per the house style. - AGENTS.md: document the publishing flow. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
biswaroop1547
force-pushed
the
release-notes-followups
branch
from
dc78ac0 to
5462fed
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.
Follow-ups to the release-notes pipeline (#13):
AGENTS.mdvoice rules;release-notes.mdxhad its punchy em dashes trimmed to commas/periods/colons (em dashes sparingly).AGENTS.mdso the end-to-end flow is visible to anyone working in the repo.Workflow validated with actionlint + shellcheck (clean). The skill side is enriched in premAI-io/fluso-development-skills#3.