chore: wire up CI and release workflows for foas module#1311
Merged
Conversation
Step 4 (final) of the tools/cli -> tools/foas module split: - Add a tools/foas/** trigger to code-health-foascli.yml so the CLI pipeline also re-runs when the foas library it depends on changes. - Add release-foas-lib.yml: a manual-dispatch workflow that releases the foas library by creating the Go submodule tag tools/foas/vX.Y.Z that external repos consume via `go get`. Tests run before the tag is created, since a published module version is immutable on the Go proxy. actionlint passes on all workflows.
yelizhenden-mdb
force-pushed
the
CLOUDP-413371-4
branch
from
fae641e to
79b63e9
Compare
yelizhenden-mdb
requested review from
andmatei,
andreaangiolillo,
drinkbird,
maks-m-mongo-leaf,
matt-condon,
saisundar and
wtrocki
andmatei
reviewed
Jun 16, 2026
yelizhenden-mdb
force-pushed
the
CLOUDP-413371-4
branch
from
896475e to
b72690e
Compare
yelizhenden-mdb
force-pushed
the
CLOUDP-413371-4
branch
from
b72690e to
9f904e6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Step 4 (final) of the
tools/cli→tools/foasmodule split. Wires up CI and release for the new library module.Previous steps
tools/foaslibrary module: chore: scaffold tools/foas library module #1308 (merged)apiversion: chore: move apiversion package into tools/foas #1309 (merged)Changes
Add a
tools/foas/**path trigger tocode-health-foascli.yml. The CLI depends on foas, so its build/test/lint/e2e pipeline should also re-run when the library changes.Add
release-foas-lib.yml— a manual-dispatch workflow that releases the foas library. Since foas is a Go library (no binaries) and is consumed as source by the CLI via Go workspaces, a "release" is simply the Go submodule tagtools/foas/vX.Y.Z. External repos (e.g.ipa-skills) then consume it with:Follow-up after merge
Once merged, I'll cut the first library tag by running the release workflow. The resulting tag
tools/foas/v0.1.0will appear under the repo's Tags - not Releases, since the library has no binary artifact.