Repository navigation
Prepare the numeric text-field prerelease cohort for production - #38
Conversation
…d-hints-for-text-fields feat: Support numeric keyboard hints for text fields (#36)
|
To preview the documentation for this pull request, visit the following URL:
|
Bugbot: review complete
|
Copilot approval · Human review neededStatus: This pull request is outside the configured approval scope. Technical evidenceRevision: |
Production publication verifiedThe production commit is
The first partial validation artifact was preserved losslessly and its ZIP digest matched GitHub before retiring that generated remote artifact to permit the same-name successful retry. Both original failure logs remain retained. The initial simultaneous CI and Pages visual deadlines were resolved by sequential retries of the same source. Domus #91 has now adopted the exact published core version and lockfile. All 162 installed package files match the approved CI tarball. The published-version integration passes 1,927 frontend tests with every coverage metric at 100% globally and per authored runtime file, followed by the independent coverage audit. Full compiled source acceptance continues in Domus. |
Promote the reviewed numeric text-field increment and verified workflow-caller locks to the production branch for the
0.1.0-next.3npm cohort.Source issue #36 and source PR #37 add the public numeric keyboard hint required by Domus #91. Source issue #34 and PR #35 complete the workflow-caller lock coverage already verified on develop.
Verified source
daba2fbbdb80da47e939d3e3d76fc76b7f195c97passes CI 44540262462, Branch Sync 44540262471, Commit/Verification 44540262543 and complete automated review 44540274743 with zero active findings.442c0c5145f65bbafde6c0915e703421a129616c. The merged tree isf14404b9475f2d19b950772bbe733c31daf0c513. Issue ✨🧑💻 - Support numeric keyboard hints for text fields #36 closed automatically and destination Branch Sync 44543550395 succeeds. Destination CI 44543550583 succeeds.Publication acceptance
Wait for the exact develop destination CI, this PR's applicable checks and review, then use the ordinary merge route. After successful CI on the exact production merge, tag that SHA as
v0.1.0-next.3through gh. The documented OIDC workflow publishes all five coordinates and verifies downloaded hashes before Domus adopts the cohort. The master push also deploys the updated Storybook Pages.The existing approval observer's
unsafe-rulesprerequisite and maintainer-authorized exception are recorded in vypdev/copilot#968. The corrected native catalog publication compatibility issue is recorded in vypdev/copilot#969.