Skip to content

ci: rebuild tag-selector dist so 1.17 is selected again - #1923

Closed
nelson-parente wants to merge 1 commit into
dapr:masterfrom
nelson-parente:ci/tag-selector-rebuild-dist
Closed

nelson-parente wants to merge 1 commit into
dapr:masterfrom
nelson-parente:ci/tag-selector-rebuild-dist

Conversation

@nelson-parente

Copy link
Copy Markdown
Contributor

Description

#1856 removed the temporary 1.17 filter from .github/tools/tag-selector/src/index.ts, but dist/index.js was not rebuilt. action.yml runs dist/index.js, so a workflow that uses this action at a commit SHA still skips every 1.17 release.

  • sdk_build.yml in this repo runs npm run build before it runs the selector, so the .NET CI matrix already includes 1.17. It is not affected.
  • dapr/js-sdk uses the action at dd2d9deb in .github/workflows/build.yml. Its E2E matrix on 2026-10-02 (run 37039524516) was 1.19.0-rc.1, 1.18.4, 1.16.20 and 1.15.14. It has no 1.17, which is still a supported runtime.

This PR is the output of npm ci, npm test (17 tests pass) and npm run build in .github/tools/tag-selector. The only change in dist/index.js is the removed filter.

With the current dapr/dapr releases, the selector (stable_count 3, rc_count 1) returns:

dist Matrix
committed (before) 1.19.0-rc.1, 1.18.4, 1.16.20, 1.15.14
rebuilt (this PR) 1.19.0-rc.1, 1.18.4, 1.17.14, 1.16.20

js-sdk gets the change only after its pin moves to a commit that includes it.

Issue reference

None. Found while checking which runtime versions the SDK CI tests for 1.19.

Checklist

  • Code compiles correctly
  • Created/updated tests (no test change: the 17 existing selector tests pass)
  • Extended the documentation

🤖 Generated with Claude Code

https://claude.ai/code/session_017JhKUDV9dbs5JDz2uwZqz5

dapr#1856 removed the temporary 1.17 filter from src/index.ts but did not
rebuild dist/index.js. The action runs dist/index.js (action.yml main),
so a workflow that uses the action at a commit SHA still skips every
1.17 release. sdk_build.yml in this repo rebuilds dist before it runs
the selector, so the .NET CI matrix is not affected.

This commit is the output of npm ci, npm test (17 tests pass) and
npm run build. The only change in dist/index.js is the removed filter.

Signed-off-by: Nelson Parente <nelson_parente@live.com.pt>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017JhKUDV9dbs5JDz2uwZqz5
@WhitWaldo

WhitWaldo commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

@nelson-parente Are you sure this is necessary? I'm looking at the outstanding "detached workflows" PR at #1919 and just re-ran the workflow from scratch. The compoute-integration-matrix properly displays the expected output as follows:

Dapr (normalized): [{"version":"1.19.0-rc.1","channel":"rc"},{"version":"1.18.4","channel":"stable"},{"version":"1.17.14","channel":"stable"},{"version":"1.16.20","channel":"stable"}]

As 1.16, 1.17, 1.18 and the RC for 1.19 are in there, I'm not sure what your issue is referring to.

Perhaps you're got a dated version of the repository on your system? You indicated that 1.15.14 is showing up in your list and that's fallen out of supported service (not N-2).

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.

2 participants