Skip to content

Comments

feat: Create version TOML file, upgrade gradle and all dependencies [COMP-1266]#583

Merged
cristianrcv merged 16 commits intomasterfrom
feat/COMP-1266-create-toml-file-and-upgrade-deps
Feb 23, 2026
Merged

feat: Create version TOML file, upgrade gradle and all dependencies [COMP-1266]#583
cristianrcv merged 16 commits intomasterfrom
feat/COMP-1266-create-toml-file-and-upgrade-deps

Conversation

@cristianrcv
Copy link
Contributor

@cristianrcv cristianrcv commented Feb 20, 2026

Description

  • Create version TOML file to automate dependency update
  • Upgrade gradle to 9.3.1
  • Upgrade dependencies to latest available stable versions
  • Upgrade tower SDK version to 1.109.0
  • Upgrade CLI version to 0.22.0

Suggestion

  • Review commit by commit as applying the new license header modified many files

@cristianrcv cristianrcv requested a review from a team February 20, 2026 08:57
@cristianrcv cristianrcv marked this pull request as draft February 20, 2026 09:07
@cristianrcv
Copy link
Contributor Author

@claude review

@cristianrcv cristianrcv marked this pull request as ready for review February 20, 2026 13:11
@cristianrcv
Copy link
Contributor Author

@swampie @tcrespog After these changes, should I release the new artifact by adding a release commit? Do you know how do we usually do in this project?

@cristianrcv cristianrcv requested review from a team and alberto-miranda February 20, 2026 13:19
@tcrespog
Copy link
Contributor

tcrespog commented Feb 23, 2026

After these changes, should I release the new artifact by adding a release commit? Do you know how do we usually do in this project?

With a dedicated PR, for example: #566. I'd suggest to bump the CLI version in the dedicated PR rather than in this PR. I wouldn't suggest to bump the API version unless there is logic that requires API changes introduced in that version (or any between the current version and the latest).

@cristianrcv
Copy link
Contributor Author

After these changes, should I release the new artifact by adding a release commit? Do you know how do we usually do in this project?

With a dedicated PR, for example: #566. I'd suggest to bump the CLI version in the dedicated PR rather than in this PR. I wouldn't suggest to bump the API version unless there is logic that requires API changes introduced in that version (or any between the current version and the latest).

Reverted CLI version update in b6dc3c5 and I will open a follow-up PR to release.

@cristianrcv cristianrcv merged commit c16624e into master Feb 23, 2026
10 checks passed
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.

5 participants