Skip to content

chore(release): bump version to 0.7.0 - #134

Merged
CybotTM merged 1 commit into
mainfrom
chore/release-0-7-0
Apr 22, 2026
Merged

chore(release): bump version to 0.7.0#134
CybotTM merged 1 commit into
mainfrom
chore/release-0-7-0

Conversation

@CybotTM

@CybotTM CybotTM commented Apr 22, 2026

Copy link
Copy Markdown
Member

Version bump in preparation for the v0.7.0 tag. Once this lands and main CI is green, a v0.7.0 tag will be pushed to trigger the Release workflow (SBOM, Cosign signing, SLSA provenance, TER publish).

What's in 0.7.0

Five new user-visible features (see Changelog):

Plus CI hygiene: mutation testing skipped on PR events, .semgrepignore for tests, fuzz testsuite name fix.

Test plan

  • CI green on all five feature PRs + docs PR (merged)
  • CI green on this version-bump PR
  • After merge: tag v0.7.0; verify Release workflow completes (SBOM / Cosign / SLSA)
  • Verify TER publish workflow runs

New user-visible features (see Documentation/Changelog.rst 0.7.0):
- provider fallback chain
- attribute-based provider registration
- BE group capability permissions
- dashboard widgets (cost + requests by provider)
- per-user AI budgets

Signed-off-by: Sebastian Mendel <github@sebastianmendel.de>
Copilot AI review requested due to automatic review settings April 22, 2026 12:52
@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@github-actions

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated approval for maintainer PR

All automated quality gates passed. See SECURITY_CONTROLS.md for compensating controls.

@github-actions github-actions Bot added the configuration Configuration changes label Apr 22, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Bumps the TYPO3 extension metadata version in preparation for tagging v0.7.0, aligning the extension’s published version with the upcoming release workflow.

Changes:

  • Update extension version in ext_emconf.php from 0.6.0 to 0.7.0.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@CybotTM
CybotTM added this pull request to the merge queue Apr 22, 2026
Merged via the queue into main with commit f822bcc Apr 22, 2026
48 checks passed
@CybotTM
CybotTM deleted the chore/release-0-7-0 branch April 22, 2026 12:56
github-merge-queue Bot pushed a commit that referenced this pull request Apr 22, 2026
## Context

The v0.7.0 tag (pushed as part of PR #134's release cycle) did not
produce artifacts. Digging in: `.github/workflows/release.yml`
references
`netresearch/typo3-ci-workflows/.github/workflows/slsa-provenance.yml@main`,
which **does not exist** in that repo (404). GitHub rejects the whole
workflow as a "workflow file issue" before any job runs.

Same reason v0.6.0's release run failed in March — pre-existing bug.

## Fix

Remove the `slsa-provenance` job. SBOM (SPDX + CycloneDX), Cosign
keyless signing, and `actions/attest-build-provenance` already run
inside the reusable `release.yml` — the separate job was redundant.

## Test plan

- [ ] Merge this fix
- [ ] Re-push the `v0.7.0` tag (delete + re-push); release workflow
should now run and produce:
  - GitHub Release with changelog
  - SBOM artifacts (.spdx.json, .cdx.json)
  - Cosign-signed archive
  - SLSA-3 attestation via `attest-build-provenance`
  - TER publish job
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

configuration Configuration changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants