Skip to content

ci: add build, security scan, and npm release workflow - #2

Open
tachhire wants to merge 2 commits into
mainfrom
ENGP-25621
Open

ci: add build, security scan, and npm release workflow#2
tachhire wants to merge 2 commits into
mainfrom
ENGP-25621

Conversation

@tachhire

@tachhire tachhire commented Aug 17, 2026

Copy link
Copy Markdown

Adds the standard Boomi build and security gate to this repo.

On every push and pull request: builds the package, runs the test suite with
coverage, and runs the secret, code-quality, and dependency scans. Any scan
failure fails the job.

On a merge to main, once that gate is green: bumps the patch version, builds
the type declarations, publishes to npm, and pushes the release commit and tag.

Also adds a coverage provider and lcov reporter so coverage reaches the
code-quality dashboard.

Requires the JFROG, SONAR, SNYK, and NPM secrets listed at the top of the
workflow file.

Adds .github/workflows/ci-anywhere.yml, which runs Boomi's standard build and
security gate on every push and pull request:

  * builds the package (npm ci + npm run build)
  * runs the test suite with coverage
  * runs the secret scan, Sonar, and the dependency scan — any failure fails
    the job

On a merge to main, and only once that gate is green, it also bumps the patch
version, builds the type declarations, publishes to npm, and pushes the release
commit and tag.

Also adds a coverage provider (@vitest/coverage-v8, pinned to the vitest already
in the lockfile) and an lcov reporter, so coverage reaches Sonar.

Requires these secrets: JFROG_TOKEN, SONAR_HOST_URL, SONAR_TOKEN, SNYK_TOKEN,
SNYK_ORG_ID, NPM_TOKEN.
@tachhire tachhire changed the title ci: add CI Anywhere workflow (build-utils install + scans) [ENGP-25621] ci: add build, security scan, and npm release workflow Aug 25, 2026
1.4.0 adds credential redaction to the build tool's log output, which matters
here because this repository's workflow logs are public. Nothing between the
previous pin and 1.4.0 touches the build or scan path for this project type.

The npm publish sequence is left in place but commented out: it needs an
NPM_TOKEN secret and write permission for the release commit, both of which are
being handled separately. Permissions drop back to contents: read until then.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant