Skip to content

Propagate changes from main into development - #1262

Merged
Wikid82 merged 13 commits into
developmentfrom
chore/sync-main-into-development
Aug 19, 2026
Merged

Propagate changes from main into development#1262
Wikid82 merged 13 commits into
developmentfrom
chore/sync-main-into-development

Conversation

@Wikid82

@Wikid82 Wikid82 commented Aug 19, 2026

Copy link
Copy Markdown
Owner

Automated PR to propagate changes from main into development.

Supersedes #1261, which couldn't be pushed to directly (its head was main itself). This branch is cut from development with main merged in and conflicts resolved:

  • .github/workflows/propagate-changes.yml: trivial placement conflict — took main's added comment (from PR chore(ci): defense-in-depth hardening against silent workflow_run trigger failures #1260) verbatim.
  • .github/workflows/release-goreleaser.yml: modify/delete conflict. main deleted this file as part of the release-please migration (superseded by release-please.yml); development's only modification since was a trivial renovate Go-version bump (verified via git show). Accepted the deletion.
  • docs/plans/current_spec.md / docs/reports/qa_report.md: auto-resolved (matched main's content exactly) — these are scratch task-tracking docs, not application state.

Also carries the same .github/skills/ diff (README.md, utility-bump-beta.SKILL.md, utility-version-check-scripts/run.sh, utility-version-check.SKILL.md) flagged in #1261 — please review before merging.

Wikid82 and others added 8 commits August 17, 2026 15:18
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Jeremy <jhatfield82@gmail.com>
The repo's default branch is development, but release-please-action
defaults its target-branch input to the repository default branch via
the API regardless of which branch the push trigger fired on. Since
release-please-config.json/.release-please-manifest.json only exist on
main (by design), the action was looking for them on development and
failing with "Missing required manifest config."
Lets a human manually re-fire branch propagation (main -> development)
when the workflow_run trigger doesn't fire on its own, without needing
to re-run the upstream Docker Build workflow. The job's `if:` condition
is extended to admit workflow_dispatch runs, since
github.event.workflow_run is unset in that context.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…to-development

# Conflicts:
#	.github/workflows/propagate-changes.yml
#	.github/workflows/release-goreleaser.yml
#	docs/plans/current_spec.md
#	docs/reports/qa_report.md
@codecov

codecov Bot commented Aug 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@Wikid82
Wikid82 marked this pull request as ready for review August 19, 2026 12:04
@github-advanced-security

Copy link
Copy Markdown
Contributor

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@github-actions

github-actions Bot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

✅ Supply Chain Verification Results

PASSED

📦 SBOM Summary

  • Components: 1753

🔍 Vulnerability Scan

Severity Count
🔴 Critical 0
🟠 High 0
🟡 Medium 5
🟢 Low 2
Total 11

📎 Artifacts

  • SBOM (CycloneDX JSON) and Grype results available in workflow artifacts

Generated by Supply Chain Verification workflow • View Details

github-actions Bot and others added 3 commits August 19, 2026 13:38
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@Wikid82
Wikid82 merged commit 4a92a78 into development Aug 19, 2026
49 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants