stackabletech / stackabletech/docker-images

chore(trino): Update major/minor versions for 26.11.0

Open
#1,657 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

scheduled-for/26.11.0
Dominant language
Dockerfile
Stars
22
Forks
6
Avg merge
16h 59m
Merged PRs (30d)
30

Description

Part of https://github.com/stackabletech/docker-images/issues/1641.

  • Add: 483
  • Deprecate: 481
  • Remove: 479

[!TIP]
Please add to the Stackable Engineering project.

Update tasks

Trino
  • Update boil-config.toml to reflect the agreed upon versions in the spreadsheet (including the removal of old versions).
  • Update boil-config.toml to the latest supported version of JVM (base and devel).
  • Update other dependencies if applicable (eg: jmx_exporter, opa_authorizer, storage_connector, etc).
  • Check other operators (getting_started / kuttl / supported-versions) for usage of the versions. Add the PR(s) to the list below.
  • Maybe update versions in tests/templates/kuttl/opa-authorization/check-opa.py.j2 (if tests fail)
  • Update the version in demos. Add the PR(s) to the list below.
  • Update versions used in the documentation repository
trino-cli
  • Update trino-cli/boil-config.toml to reflect the agreed upon versions in the spreadsheet (including the removal of old versions).
  • Upload new version (see trino-cli/upload_new_trino_version.sh scripts).
  • Update boil-config.toml to the latest supported version of JVM (base and devel).
  • Check other operators (getting_started / kuttl / supported-versions) for usage of the versions. Add the PR(s) to the list below.
  • Update the version in demos. Add the PR(s) to the list below.
  • Update versions used in the documentation repository

Related Pull Requests

[!TIP]
Delete any items that do not apply so that all applicable items can be checked.
For example, if you add release notes to the documentation repository, you do not need the latter two criteria.

  • Link to the docker-images PR (product update)
  • Link to the operator PR (getting_started / kuttl / supported-versions)
  • Link to any other operator PRs (getting_started / kuttl)
  • Link to demo PR (raise against the main branch)
  • Link to the Release Notes PR in the documentation repo (if not a comment below)

Acceptance

[!TIP]
This list should be completed by the assignee(s), once respective PRs have been merged. Once all items have been
checked, the issue can be moved into Development: Done.

  • Can build image (either locally, or in CI)
  • All kuttl tests pass (either locally, or in CI)
  • Release notes added to documentation and linked as a PR above
  • Release notes written in a comment below
  • Applicable release-note label added to this issue
Testing instructions
# Where x.y.z is the new version added in this PR
boil build trino=x.y.z --strip-architecture --load
boil build trino-cli=x.y.z --strip-architecture --load

kind load docker-image oci.stackable.tech/sdp/trino:x.y.z-stackable0.0.0-dev
kind load docker-image oci.stackable.tech/sdp/trino-cli:x.y.z-stackable0.0.0-dev

# Change directory into the trino-operator repository and update the
# product version in tests/test-definition.yaml
./scripts/run-tests --test-suite smoke-latest # or similar

Please consider updating this template if these instructions are wrong, or
could be made clearer.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the agreed versions in the spreadsheet, then inspect boil-config.toml and trino-cli/boil-config.toml. Review trino-cli/upload_new_trino_version.sh and the referenced KUTTL, demo, and documentation version locations. Done means the images build, the applicable tests pass, and the required related PRs and release notes are linked.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, shell
Domain
devops, release, testing
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.