chore(deps): bump bigins/imanager 2.0.2 -> 2.1.0#64
Merged
Conversation
iManager 2.1.0 shipped on 2026-05-16 with the schema-setup ergonomics surface (16 Field::* static factories, 13 fluent setters, CategoryRepository::ensure() + FieldRepository::ensure() upsert-by-natural-key) plus the corrected Imanager::VERSION constant and the new ReleaseConsistencyTest that gates future forgotten bumps. Lock now resolves bigins/imanager: ^2.0 to 2.1.0 (commit f38bce7 = the chore(release): cut 2.1.0 merge). Scriptor's own code can now use Field::text(...)->required()->indexed() and $fields->ensure(...) in any future schema-setup work, instead of the verbose new Field(null, $cat->id, 'name', 'Label', FieldType::Text, required: true, ...) constructors. Local boot smoke: Imanager::VERSION reports 2.1.0; Field::text reflects on Imanager\Domain\Field. Live smoke against the currently-deployed scriptor.cms: frontend 200, editor auth page 200 (unchanged since this PR only bumps the lock, no Scriptor code change). No Scriptor source uses the new surface yet — that comes when schema-touching work happens. This PR is the enabler.
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.
iManager 2.1.0 shipped on 2026-05-16 with the schema-setup ergonomics surface (16 Field::* static factories, 13 fluent setters, CategoryRepository::ensure() + FieldRepository::ensure() upsert-by-natural-key) plus the corrected Imanager::VERSION constant and the new ReleaseConsistencyTest that gates future forgotten bumps.
Lock now resolves bigins/imanager: ^2.0 to 2.1.0 (commit f38bce7 = the chore(release): cut 2.1.0 merge). Scriptor's own code can now use Field::text(...)->required()->indexed() and $fields->ensure(...) in any future schema-setup work, instead of the verbose new Field(null, $cat->id, 'name', 'Label', FieldType::Text, required: true, ...) constructors.
Local boot smoke: Imanager::VERSION reports 2.1.0; Field::text reflects on Imanager\Domain\Field. Live smoke against the currently-deployed scriptor.cms: frontend 200, editor auth page 200 (unchanged since this PR only bumps the lock, no Scriptor code change).
No Scriptor source uses the new surface yet — that comes when schema-touching work happens. This PR is the enabler.