Goal: supersede deploy v0.1.6 (pins unavailable backend:2.3.0) with a new immutable bundle pinning published frontend:1.2.1 and backend:2.3.1. Related deploy#12 and backend#129.
Acceptance criteria:
Backend 2.3.1 image publishing job succeeds before bundle tag is created.
release.env pins frontend:1.2.1 and backend:2.3.1; README states exactly what is and is not verified.
Existing v0.1.6 tag stays intact; new annotated bundle tag is created on reviewed main commit after local gates.
Operator can run the new bundle tag after validating pull from deployment host.
No changes to deploy.sh or production state.
Goal: supersede deploy v0.1.6 (pins unavailable backend:2.3.0) with a new immutable bundle pinning published frontend:1.2.1 and backend:2.3.1. Related deploy#12 and backend#129.
Acceptance criteria:
- Backend 2.3.1 image publishing job succeeds before bundle tag is created.
- release.env pins frontend:1.2.1 and backend:2.3.1; README states exactly what is and is not verified.
- Existing v0.1.6 tag stays intact; new annotated bundle tag is created on reviewed main commit after local gates.
- Operator can run the new bundle tag after validating pull from deployment host.
No changes to deploy.sh or production state.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal: supersede deploy v0.1.6 (pins unavailable backend:2.3.0) with a new immutable bundle pinning published frontend:1.2.1 and backend:2.3.1. Related deploy#12 and backend#129.
Acceptance criteria:
No changes to deploy.sh or production state.