Skip to content

plans: per-entry changelog layout investigation (toolshed#4498)#4499

Draft
Copilot wants to merge 2 commits into
mainfrom
copilot/investigate-new-changelog-layout
Draft

plans: per-entry changelog layout investigation (toolshed#4498)#4499
Copilot wants to merge 2 commits into
mainfrom
copilot/investigate-new-changelog-layout

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented May 11, 2026

Adds plans/per-entry-changelog-4498.md — the investigation report for supporting the new per-entry changelog layout for Envoy.

The document covers:

  • Summary of the problem and approach
  • Toolshed changes (5 PRs): typing relaxation, new RST-directory aggregator, write_version/write_current/write_date/changes_for_commit updates, per-entry checker in envoy.code.check, and tests
  • Envoy changes (4 PRs): migrating current.yaml to per-entry layout, BUILD filegroup updates, docs/RELEASE.md updates, envoy-release.yml smoke-test
  • Suggested landing order with sequencing constraints and PyPI publish gate
  • Open questions on design decisions (date sentinel, squash timing, git add limits, backward compat, Bazel cache, is_pending fallback, duplicate_current check)

No code changes — planning document only.

@netlify
Copy link
Copy Markdown

netlify Bot commented May 11, 2026

Deploy Preview for nifty-bassi-e26446 ready!

Name Link
🔨 Latest commit 68a0ffc
🔍 Latest deploy log https://app.netlify.com/projects/nifty-bassi-e26446/deploys/6a020a7787fc94000814ebfc
😎 Deploy Preview https://deploy-preview-4499--nifty-bassi-e26446.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

- Spell out layout-dispatch requirement in Toolshed PR 3 so legacy
  branches without `changelogs/current/` keep using the YAML reader/writer.
- Resolve the "historical branches" and `is_pending` open questions.
- Note `duplicate_current` in `envoy.code.check` continues to work
  unchanged because the slim `current.yaml` still exists.
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