Skip to content

The weekly Backstage update has not opened a pull request since July #77

Closed

Description

@ecv

Summary

The scheduled job that moves the portal onto each new Backstage release has failed on all ten runs since early July, so it has never opened a pull request for anyone to review.

The portal still builds against the Backstage release from 6 July while upstream has moved two minor versions ahead. No dependency or security update has reached the main branch in those two months.

What runs for users has drifted further still, because the newest release tag predates seven merged changes, including the catalog vocabulary work.

Acceptance criteria

  • The weekly job finishes and opens a pull request carrying the new Backstage versions
  • That pull request carries a lock file a clean install accepts without modification
  • A future run that produces an inconsistent lock file fails the job instead of opening a pull request

Releasing

Merging the update does not put it in front of users, and cutting a tag to do that is a separate decision.

Important

Staging tracks the main branch continuously, but production follows the newest stable tag on an open range with no pin. A tag reaches production within minutes of being cut, and no soak period stands between the two, so the first release after this fix wants deliberate timing rather than a reflex tag.

Activity

  1. ecv commented on Sep 12, 2026

    @ecv
    ContributorAuthor

    Reopened, because this closed when #78 merged, before the weekly job has run with the fix. Its last three scheduled runs all failed.

    The next scheduled run is Monday 14 September at 06:00Z. This closes once that run finishes and opens a pull request whose lock file installs cleanly, or earlier if someone starts the job by hand.

  2. reopened this on Sep 12, 2026
  3. ecv commented on Sep 12, 2026

    @ecv
    ContributorAuthor

    The job ran by hand at 19:56Z today and finished green. It bumped the packages, passed the immutable lock file check it now runs before opening anything, and opened #79.

    No checks ran on that pull request, because the job opens it with the default workflow token. That gap is tracked in #80.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions