Skip to content

Conversation

@anithapriyanatarajan
Copy link
Contributor

Changes

This pull request updates Tekton release URLs throughout the documentation and scripts to use the new infra.tekton.dev domain instead of the previous storage.googleapis.com URLs. This PR also removes the release_yaml_oracle function since all components now use infra.tekton.dev

Migration to new Tekton release URL domain:

  • Updated all references to Tekton release YAMLs in docs/install.md, tekton/setup-release-from-scratch.md, and hack/fetch-releases.sh to use https://infra.tekton.dev/tekton-releases/ instead of https://storage.googleapis.com/tekton-releases/.

Script cleanup and refactoring:

  • Removed the release_yaml_oracle function from hack/fetch-releases.sh, as it is no longer needed with the unified URL format.
  • Refactored the pruner release YAML fetching logic to use the standard release_yaml function, simplifying the code and ensuring consistency.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Release Notes

NONE

@tekton-robot tekton-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. release-note-none Denotes a PR that doesnt merit a release note. labels Dec 4, 2025
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Dec 4, 2025
@anithapriyanatarajan
Copy link
Contributor Author

Marked hold to assess and test in Openshift cluster if the changes are working fine.

@anithapriyanatarajan
Copy link
Contributor Author

/kind cleanup

@tekton-robot tekton-robot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Dec 4, 2025
@anithapriyanatarajan anithapriyanatarajan changed the title WIP cleanup: replace GCS buckets with OCI buckets cleanup: replace GCS buckets with OCI buckets Dec 4, 2025
@tekton-robot tekton-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Dec 4, 2025
@jkhelil
Copy link
Member

jkhelil commented Dec 5, 2025

/approve

@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jkhelil

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 5, 2025
@mbpavan
Copy link
Contributor

mbpavan commented Dec 5, 2025

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 5, 2025
@jkhelil
Copy link
Member

jkhelil commented Dec 5, 2025

/lgtm

@tekton-robot tekton-robot merged commit 350b708 into tektoncd:main Dec 5, 2025
13 checks passed
@anithapriyanatarajan
Copy link
Contributor Author

/cherry-pick release-v0.78.x

@tekton-robot
Copy link
Contributor

Cherry-pick to release-v0.78.x successful!

A new pull request has been created to cherry-pick this change to release-v0.78.x.

Please review and merge the cherry-pick PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants