Repository navigation
Release 0.1.1 - #78
Merged
Merged
Conversation
Everything accumulated since the initial release becomes 0.1.1: username-based password login, the explicit identity-linking mechanism, the token issuer registry, the two-factor API, and the fixes listed in the section. Cut as a new version rather than by moving v0.1.0. The repository carries a "release tags are final" ruleset that refuses an update to refs/tags/v*, and a moved tag would not reach a consumer whose composer cache already holds a dist archive under that name -- it would report success and unpack the old code.
This was referenced Nov 13, 2026
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
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.
Summary
Cuts 0.1.1 from everything accumulated since the initial release —
## [Unreleased]becomes## [0.1.1] - 2026-11-13, with a fresh empty Unreleased above it and the compare links updated.Why a new number rather than moving
v0.1.0Two reasons, and either is sufficient:
release tags are finalruleset blockingupdateanddeletiononrefs/tags/v*, so a force-move is refused.that name.
composer updatereports success, resolvesv0.1.0, and unpacks what it cached thefirst time — the failure is silent and points nowhere useful.
What this unblocks
laranail/authkit-social-loginneedsIdentityLinkingInterfaceto build its explicit connectflow (authkit-social-login#12). That
interface is on
mainbut 404s atv0.1.0, which predates both merges, so the consumer cannotresolve it until a tag carries it.
No code changes — CHANGELOG only.