Repository navigation
ci(stacklet): add nightly Stacklet CI and harden Stacklet workflows (ENG-9458) - #17
Merged
Merged
Conversation
albertodonato
force-pushed
the
ack/stacklet-ci-jobs
branch
from
October 27, 2026 10:34
6e76794 to
5250d2c
Compare
albertodonato
force-pushed
the
ack/stacklet-ci-jobs
branch
from
October 27, 2026 10:52
5250d2c to
0993033
Compare
albertodonato
marked this pull request as ready for review
October 27, 2026 16:03
…ENG-9458) [ENG-9458](https://stacklet.atlassian.net/browse/ENG-9458) ### what - add `stacklet-ci.yml`, running nightly at 07:00 UTC and on manual dispatch: - Python unit tests, including the 100% coverage check on `superset/sql`, through `stacklet/github-tooling`'s `run-script` v1.1.0, with tools from the `stacklet-ci` mise env (`mise.stacklet-ci.toml`, locked in `mise.stacklet-ci.lock`) - Stacklet frontend Jest tests (`src/stacklet`) and frontend lint, installing `@stacklet/ui` with a CodeArtifact token from the `PUBLISH_ROLE_ARN` role shared with `stacklet-image` - a Slack message at the start, updated with the result, as in redash's `e2e-tests.yml` - add StepSecurity Harden Runner (policy store, skipped without `STEP_SECURITY_API_KEY`) to every job in `stacklet-ci`, `stacklet-image` and `stacklet-sync-upstream-tags` - give the tag-sync job explicit `contents: read` permissions - add a `mise.toml` enabling lockfiles for all supported platforms, as in `stacklet/github-tooling` ### why Upstream's CI workflows are disabled in the fork, so nothing runs the unit tests on Stacklet changes, and the Stacklet frontend tests have never run in CI. ### testing - `actionlint` and `zizmor` on the Stacklet workflows - a temporary `pull_request` trigger runs the workflow on this PR; it is removed before merge ### docs n/a Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
albertodonato
force-pushed
the
ack/stacklet-ci-jobs
branch
from
October 27, 2026 16:04
0993033 to
7ae62a5
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
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.
ENG-9458
what
stacklet-ci.yml, running nightly at 07:00 UTC and on manualdispatch:
superset/sql, throughstacklet/github-tooling'srun-scriptv1.1.0, with tools from the
stacklet-cimise env(
mise.stacklet-ci.toml, locked inmise.stacklet-ci.lock)src/stacklet) and frontend lint,installing
@stacklet/uiwith a CodeArtifact token from theci-github-actionsroleredash's
e2e-tests.ymlSTEP_SECURITY_API_KEY) to every job instacklet-ci,stacklet-imageandstacklet-sync-upstream-tagscontents: readpermissionsmise.tomlenabling lockfiles for all supported platforms, asin
stacklet/github-toolingwhy
Upstream's CI workflows are disabled in the fork, so nothing runs the
unit tests on Stacklet changes, and the Stacklet frontend tests have
never run in CI.
testing
actionlintandzizmoron the Stacklet workflowspushtrigger on this branch runs the workflow; it isremoved before merge
docs
n/a
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com