• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

valkyrjaio / ci-phpunit-php / 31137074877
100%

Build:
DEFAULT BRANCH: 26.x
Ran 07 Aug 2026 01:09AM UTC
Jobs 1
Files 3
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

07 Aug 2026 01:08AM UTC coverage: 100.0%. Remained the same
31137074877

push

github

web-flow
[Dependency] fix: Track the released framework instead of the 26.x branch (#203)

# Description

The PHPUnit tooling suite required `valkyrja/valkyrja` at `26.x-dev`. A
branch
constraint moves its reference on every upstream commit, so the lock
file is
stale minutes after it is written. The release gate asks whether
`composer
update` can improve on the lock, and against a branch constraint the
answer is
almost always yes. Every automated release since 1 August has failed on
it.

The constraint was added on 24 April with `ServiceProviderTestCase`,
which wires
a real `Container`, `Env`, `ApplicationContract`, and `ConfigContract`.
At that
date the only tagged 26.x release was `v26.0.0` from 31 March, and the
APIs that
test case wires were still moving on the branch. The branch constraint
was the
only way to build against them.

That reason has expired. The framework has tagged through `v26.10.0`,
and the
suite passes against it: 31 tests, 41 assertions, no failures. After
this change
`composer update --dry-run` reports `Nothing to modify in lock file`, so
the gate
reads a stable lock and the release proceeds.

The constraint now names a released version, which the dependency update
workflow
raises the same way it raises every other constraint in this file.

This removes one source of gate failures. It does not remove them all:
the gate
reports the whole lock, so a transitive package that publishes between
the
dependency update and the release still blocks it. `valkyrjaio/.github`
holds
that fix.

The suite no longer tests against the 26.x branch before it is tagged.
That
signal belongs in a scheduled run against the branch, not in the
constraint the
release gate reads, where it costs a release each day.

## Types of changes

- [ ] Improvement _(non-breaking change which improves code)_
- [X] Bug fix _(non-breaking change which fixes an issue)_
- [ ] New feature _(non-breaking change which adds functionality)_
- [ ] Deprecation _(breaking change which re... (continued)

33 of 33 relevant lines covered (100.0%)

3.24 hits per line

Jobs
ID Job ID Ran Files Coverage
1 31137074877.1 07 Aug 2026 01:09AM UTC 3
100.0
GitHub Action Run
Source Files on build 31137074877
  • Tree
  • List 3
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #31137074877
  • b1eda956 on github
  • Prev Build on 26.x (#31101522529)
  • Next Build on 26.x (#31166469057)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc