Repository navigation
📝🧑💻 - Document patch release preparation and retained build artifacts #166
Description
Is there an existing issue for this?
- I have searched the existing issues.
What part of the documentation needs an update?
Other
Describe the documentation update
Document the maintainer-requested patch release and the actual Copilot deployment flow. All publishable metadata, WebAssembly and CLI native libraries are generated or compiled during deployment preparation. macOS, Linux and Windows build jobs pass forward their committed outputs; all final candidate gates validate one exact commit before promotion and publication. Explain where these artifacts are retained, how the ten packages publish in dependency order after candidate acceptance, and how recovery reuses the immutable accepted version.
Align CI and runner documentation with trusted same-repository PR/develop triggers, the current vypdev runner labels, rootless private Linux dependencies, private Flutter settings, the iOS simulator backport and isolated Android Gradle/JDK state. Distinguish disposable CI test-host builds from publishable release artifacts. Correct obsolete sudo, host-package-repair and preinstalled-SDK claims.
Why is this update needed?
The operational documentation still describes obsolete runner setup and does not clearly explain that publication waits for every platform build and candidate gate. The maintainer selected a patch release and explicitly requested that publishable generation/compilation happen in Copilot's deployment phase. The latest stable tag is v1.5.0, so the expected next patch is 1.5.1. PR #165 is merged and develop's 40 checks passed.
Additional resources
- Fix iOS and Android CI and require Action version tags #165
- docs/development/ci-cd.md
- docs/development/self-hosted-ci.md
- docs/development/release-process.md
- docs/deployment/RUNBOOK.md
- .github/workflows/release_workflow.yml
- .github/workflows/publish_workflow.yml
Additional context or comments
The maintainer authorized updating and merging the documentation into develop, then initiating the patch release through the installed Copilot system. Preserve all Copilot configuration, workflows, guidance and branch ownership. Keep Action references on version tags. Do not generate release artifacts, change package versions, create tags or publish packages from the local documentation task; deployment preparation owns those outputs. Native CI validation builds remain in place.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
[-]Document patch release preparation and retained build artifacts[/-][+]📝 - Document patch release preparation and retained build artifacts[/+]vypbot commentedon Oct 25, 2026
Hi! I’m @vypbot, the Copilot assistant for this repository.
I can answer questions, explain the codebase, propose implementation and test plans, review issues and pull requests for potential bugs or security problems, and help authorized maintainers apply changes.
Try
/copilot helpto see the available commands, or mention @vypbot with your question.[-]📝 - Document patch release preparation and retained build artifacts[/-][+]📝🧑💻 - Document patch release preparation and retained build artifacts[/+]6 remaining items
vypbot commentedon Oct 25, 2026
Issue closed — historical progress
Current status: closed as completed.
The last estimate is retained below as history. Closure does not certify a new percentage, tests, or branch alignment.
Action required: none for this closed issue. If work continues, reopen the issue; a fresh assessment can update this same card.
Last assessment before closure (historical)
Merge pull request #167 from vypdev/docs/166-document-patch-release-p…