Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

chore(airflow): Update patch versions for 26.11.0

Offen
#1,701 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
45/100
Issue-Typ
Refactoring
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
docker
Bereich
devops

Rechercherichtung

The core edit is replacing 3.3.1 with 3.3.2 in boil-config.toml, after checking the agreed versions in the linked spreadsheet. Then run airflow/download_constraints.sh to refresh the constraints file. Done means the new version builds locally with boil build airflow=3.3.2 or in CI, and the smoke tests in the airflow-operator repo pass.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

scheduled-for/26.11.0

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

  • Replace: 3.3.1 with 3.3.2 (no deprecation, as it was only added in #1645)

Update tasks

  • Update boil-config.toml to reflect the agreed upon versions in the spreadsheet (including the removal of old versions).
  • Download new constraints file (see airflow/download_constraints.sh).
  • Update other dependencies if applicable (eg: python, statsd_exporter, cyclonedx-bom, etc).
  • Check other operators (getting_started / kuttl / supported-versions) for usage of the versions. Add the PR(s) to the list below.
  • Ensure prerequisites are up to date (required-external-components.adoc).
  • Update the version in demos. Add the PR(s) to the list below.

[!TIP]
The tests might fail to pull an image if the spark version is not updated in the private repo as part
of the Spark version bumps.
This is usually only discoverable after branching, because there are always old versions for 0.0.0-dev.

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 operator PR (getting_started / kuttl)
  • 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 3.3.2 is the new version added in this PR
boil build airflow=3.3.2 --strip-architecture --load

kind load docker-image oci.stackable.tech/sdp/airflow:3.3.2-stackable0.0.0-dev

# Change directory into the airflow-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.

Vorherrschende Sprache
Dockerfile
Sterne
22
Forks
7
Ø Merge
2 T. 19 Std.
Gemergte PRs (30 T.)
37

Entwicklungsumgebung

  • Kein Dockerfile und keine Docker-Compose-Datei
  • Hat eine Pull-Request-Vorlage
  • Kein Beitragsleitfaden

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus stackabletech/docker-images

Alle Issues in stackabletech/docker-images

Ähnliche Issues

Weitere Issues zu DevOps

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.