Factory: versions and tags, releases, retry settings, pull of the default branch
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
06c1b8df1b
commit
cb1e31b6e9
13 files changed
+1082
-19
No files matched your search
@@ -3,6 +3,31 @@
|
||||
All notable changes to CodeCraft. Versions follow [Semantic Versioning](https://semver.org/);
|
||||
until 1.0, minor versions may contain breaking changes.
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Added
|
||||
|
||||
- **Factory versions and tags.** Every merged factory issue (merged through the factory or on the forge)
|
||||
gets a version: the patch number goes up with each issue (0.1.0 → 0.1.1); the issue that completes a
|
||||
milestone (the last open `M1.x` issue) raises the minor number and restarts the patch (0.0.7 → 0.1.0).
|
||||
The factory commits a `VERSION` file on the default branch, tags the commit `vX.Y.Z`, closes the issue
|
||||
and notes the version in it. The version shows on the repository tile. Versioning starts with the next
|
||||
merged issue; issues that were done before are not counted.
|
||||
- **Factory release (0.x → 1.0.0 and on).** The new "Release" button makes a release you choose the
|
||||
version of: `VERSION`, tag, the Docker image for amd64 and arm64 (buildx, pushed to the registry of the
|
||||
image name), the source zip and further files, and the release on the forge (Gitea and GitHub attach the
|
||||
files; GitLab gets the release without attachments). How to build is described in
|
||||
`.factory/release.json` in the repository (`image`, `platforms`, `dockerfile`, `context`,
|
||||
`build_args`, `commands`, `files`, `name`); without it only tag, release and source zip are made. The
|
||||
dialog shows the recipe first, because its commands run on the server outside the sandbox.
|
||||
- The image now contains the buildx plugin.
|
||||
- **The factory's checkout of the default branch is pulled** (fast-forward) after every fetch, and right after
|
||||
a merge is detected and the version commit is pushed – before, the review read the files of the first clone.
|
||||
Local changes or a diverged branch are left alone with a warning.
|
||||
- **Settings for repetitions** per repository: *Rework rounds* (how often a failed acceptance sends the
|
||||
issue back to the build, default 2, 0 = never) and *Tries* per phase (how often a phase is repeated after
|
||||
a technical failure such as a timeout, default 2).
|
||||
|
||||
## [v202611-00048] – 2026-11-16
|
||||
|
||||
### Fixed
|
||||
|
||||
Reference in new issue
Block a user