Skip to content

docs: distill release automation verification lesson - #71

Open
albert20260301 wants to merge 1 commit into
altertable-ai:mainfrom
albert20260301:docs/distill-release-automation-20261002
Open

albert20260301 wants to merge 1 commit into
altertable-ai:mainfrom
albert20260301:docs/distill-release-automation-20261002

Conversation

@albert20260301

Copy link
Copy Markdown
Contributor

Summary

  • Add the durable release-automation verification rule learned from the invalid generated CLI v1.10.0 release PR.
  • Require checking a successor release PR contains only commits after the preceding tagged and published release.

Impact

This updates maintainer memory only. It does not change product code, release configuration, or API behavior.

Validation

  • make lint
  • git diff --check
  • make check-links could not run because lychee is not installed on this host.

@albert20260301

Copy link
Copy Markdown
Contributor Author

@francoischalifour could you review this?

I picked you because the recent history of MEMORY.md identifies you as its last non-Albert author. CI is green for the Markdown lint and diff checks; the link check is unavailable on this host because lychee is not installed. The main review focus is whether this is a durable release-automation invariant rather than transient incident detail.

@albert20260301

Copy link
Copy Markdown
Contributor Author

@francoischalifour could you take a look when you have time?

I selected you from the recent MEMORY.md history. CI remains green; the review focus is whether the release-automation note captures a durable invariant rather than transient incident detail.

@albert20260301

Copy link
Copy Markdown
Contributor Author

@francoischalifour this has remained review-gated for four days since the last follow-up. Both checks are green and no changes have been requested. Could you review whether the release-automation lesson is a durable invariant rather than transient incident detail?

@albert20260301

Copy link
Copy Markdown
Contributor Author

@francoischalifour this remains review-gated three days after the prior follow-up. Both CI checks are green and there are no requested changes. Could you review whether the release-automation lesson captures a durable invariant rather than transient incident detail?

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.

1 participant