Skip to content

Conversation

@vaind
Copy link
Contributor

@vaind vaind commented Sep 19, 2025

Summary

  • Fix CI test failures that occurred after the 2.14.0 release
  • Update test scripts to dynamically determine the latest version instead of hardcoding values

Changes

updater/tests/update-dependency.Tests.ps1

  • Changed from using git ls-remote --sort to using the same version sorting logic as the actual update-dependency.ps1 script
  • This ensures consistent version resolution between tests and production code
  • Fixes test failures caused by mixed tag prefixes (v2.13.1 vs 2.14.0)

updater/tests/workflow-args.sh

  • Changed from hardcoded "latest" to dynamically returning the actual latest tag using git describe --tags --abbrev=0
  • Ensures the workflow test outputs remain empty (as expected) since no update will be needed
  • Future-proofs the test against new releases

Test plan

  • Local Pester tests pass (22/22)
  • update-dependency.ps1 shows no update needed for workflow-args.sh (originalTag=latestTag=2.14.0)
  • CI workflow tests should now pass

Root Cause

After the 2.14.0 release, the test scripts were still expecting "latest" while the updater found a newer version (2.14.0), causing the workflow to set outputs when the tests expected them to be empty.

🤖 Generated with Claude Code

- Fix update-dependency.Tests.ps1 to use same version sorting logic as actual script
- Update workflow-args.sh to dynamically return latest tag using git describe
- Ensures CI tests remain stable across releases without manual updates

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@vaind vaind changed the title fix(ci): fix CI test failures after 2.14.0 release test: fix CI test failures after 2.14.0 release Sep 19, 2025
- Remove git describe fallback complexity
- Always use git ls-remote for consistency with PowerShell script
- More reliable in CI environments and shallow clones
- Test now expects actual version number instead of hardcoded 'latest'
- Verifies originalTag == latestTag to ensure no update is needed
- Maintains expectation of empty outputs when no update occurs
@vaind vaind marked this pull request as ready for review September 19, 2025 19:45
- Test now accepts either 'latest' or actual version number format
- Maintains backward compatibility while supporting dynamic versioning
- Still ensures originalTag == latestTag for no-update scenario
@vaind vaind merged commit 6c79cf7 into main Sep 19, 2025
22 checks passed
@vaind vaind deleted the fix-ci-tests-after-2.14.0 branch September 19, 2025 19:49
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