A frontend release is more than a source commit. It includes the resolved dependency tree, install-time code, build configuration, emitted files, and cache behavior after deployment. This track follows a case dashboard that must load the same reviewed application in two regions and survive a rollback. It covers locked installs, dependency admission, browser asset integrity, and atomic manifest rollout. Each lesson separates evidence that a build is repeatable from evidence that a particular artifact is safe to execute.
Topics in this track
- Locked Dependency Resolution and Clean Installs — Make the reviewed source tree resolve the same package graph in continuous integration.
- Dependency Admission, Install Scripts, and Provenance — Review new package authority and build-time code before it enters the release graph.
- External Asset Integrity and Module Resolution — Pin the browser bytes of external scripts and keep module resolution tied to a reviewed release.
- Artifact Manifest, Rollout, and Rollback Coherence — Promote an immutable frontend artifact with its asset list and keep older documents loadable.
Prerequisite paths
Continuous Integration and Release Gates; Dependency Integrity and Update Window.
Neighbor track
Embedded Interfaces and Cross-Window Contracts.
Practice path
Build Project: frontend artifact promotion and rollback and check decisions in Web Development: embedded interfaces and build integrity quiz.