Skip to content

ci: track upstream MoQ releases and other dependencies - #11

Open
pzanella wants to merge 1 commit into
chore/upgrade-moq-jsfrom
ci/upstream-tracking
Open

pzanella wants to merge 1 commit into
chore/upgrade-moq-jsfrom
ci/upstream-tracking

Conversation

@pzanella

Copy link
Copy Markdown
Owner

Depends on #10. Merge #8, #9 and #10 first; this PR then moves to main.

Why

MoQ ships releases almost every week. This repo fell three minor versions behind before anyone noticed. This PR makes the drift visible as soon as it starts.

What

  • .github/workflows/upstream-check.yml runs every Monday at 06:00 UTC, or by hand. .github/scripts/upstream-check.sh compares the pinned moq-relay, moq-cli, @moq/net and @moq/msf with the newest releases. When a pin is behind, it opens (or updates) one issue, "Upstream MoQ updates available", with a table. It closes the issue when all pins are up to date. The report is also in the run summary.
  • .github/dependabot.yml: weekly grouped PRs for GitHub Actions, root npm and dashboard/ npm. @moq/* is ignored on purpose: these must move together with the binaries and the smoke tests (CONTRIBUTING, "Bump pinned versions together").
  • lint job: fails when the moq-relay pin in Containerfile and ci.yml, or the @moq/net pin in package.json and dashboard/package.json, don't match.
  • CONTRIBUTING and CHANGELOG updated.

Tests

- upstream-check.yml runs every Monday and keeps one issue up to date
  when moq-relay, moq-cli, @moq/net or @moq/msf is behind the newest
  release.
- Dependabot opens weekly grouped PRs for GitHub Actions and npm
  packages, except @moq/*, which move together with the binaries.
- The lint job fails when the copies of a pinned version don't match.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant