chore(main): release crosswake_rulestead 0.1.0 - #39
Open
szTheory wants to merge 1 commit into
Open
Conversation
szTheory
force-pushed
the
release-please--branches--main--components--crosswake_rulestead
branch
from
June 30, 2026 13:58
63f7144 to
ca56ca6
Compare
szTheory
force-pushed
the
release-please--branches--main--components--crosswake_rulestead
branch
from
July 2, 2026 12:39
ca56ca6 to
461016b
Compare
szTheory
force-pushed
the
release-please--branches--main--components--crosswake_rulestead
branch
3 times, most recently
from
July 4, 2026 01:26
9383ecc to
9eb41f3
Compare
szTheory
force-pushed
the
release-please--branches--main--components--crosswake_rulestead
branch
from
July 19, 2026 01:20
9eb41f3 to
27a7ff6
Compare
szTheory
force-pushed
the
release-please--branches--main--components--crosswake_rulestead
branch
2 times, most recently
from
July 28, 2026 00:16
fdaaf10 to
94068f0
Compare
This was referenced Jul 28, 2026
szTheory
force-pushed
the
release-please--branches--main--components--crosswake_rulestead
branch
from
July 28, 2026 18:20
94068f0 to
6a261a2
Compare
szTheory
added a commit
that referenced
this pull request
Jul 28, 2026
`crosswake_rulestead` and `crosswake_rindle` have never published to Hex (hex.pm API returns 404 for both; no `crosswake_rulestead-v0.1.0` / `crosswake_rindle-v0.1.0` tags exist). Their Release PRs (#39, #38) are open and unmerged. But the docs advertised them as live: - `guides/companion_compatibility.md` listed both at version `0.1.0` and linked `hexdocs.pm/crosswake_{rulestead,rindle}` — both dead — and the prose claimed adding `crosswake_rindle` "resolves cleanly" today. - `.planning/RETROSPECTIVE.md` claimed v16.0 shipped "two live Hex publishes". - `.planning/PROJECT.md` and `.planning/MILESTONES.md` described all five companions as extracted "Hex packages" without distinguishing published from merely release-wired. Only `CHANGELOG.md` hedged correctly. The compat matrix already had a sanctioned vocabulary for this: the merge-blocking drift test (`test/crosswake/proof/phase132_compat_matrix_drift_test.exs:211`) accepts a `Current Version` cell of `unpublished`, and its own remediation text says to use it pre-publish. The rows were simply wrong. Rows stay (the drift test bans phantom rows and derives the `~> 0.1` floor from each package's `crosswake_dep/0`); only the publish-status claim and the dead links change. No publish is performed here. This corrects the claim rather than shipping to match it — a deliberate choice, since Hex publishes are irreversible and `packages/crosswake_rulestead/CHANGELOG.md` still carries core-inherited history that would ship permanently. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
szTheory
force-pushed
the
release-please--branches--main--components--crosswake_rulestead
branch
from
July 29, 2026 00:03
6a261a2 to
f0011eb
Compare
szTheory
force-pushed
the
release-please--branches--main--components--crosswake_rulestead
branch
from
July 30, 2026 20:21
f0011eb to
d24cbfe
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
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.
🤖 I have created a release beep boop
0.1.0 (2026-07-30)
Bug Fixes
This PR was generated with Release Please. See documentation.