Skip to content

[cherry-pick: release-v1.6.x] fix: replace kodata LICENSE symlinks with actual files#10385

Open
tekton-robot wants to merge 2 commits into
release-v1.6.xfrom
cherry-pick-10358-to-release-v1.6.x
Open

[cherry-pick: release-v1.6.x] fix: replace kodata LICENSE symlinks with actual files#10385
tekton-robot wants to merge 2 commits into
release-v1.6.xfrom
cherry-pick-10358-to-release-v1.6.x

Conversation

@tekton-robot

Copy link
Copy Markdown
Collaborator

This is a cherry-pick of #10358


ko v0.19.0 introduced strict enforcement that kodata symlinks must not resolve outside the kodata root (ko-build/ko#1619). The existing LICENSE -> ../../../LICENSE symlinks in all cmd/*/kodata/ directories resolve to the repo root, which ko now rejects when tarring for any non-kind registry (including CI).

Replace the symlinks with actual copies of the LICENSE file.

Changes

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
  • Has Tests included if any functionality added or changed
  • pre-commit Passed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Fixes #10357

Release Notes

NONE

khrm and others added 2 commits July 2, 2026 21:24
ko v0.19.0 introduced strict enforcement that kodata symlinks must not
resolve outside the kodata root (ko-build/ko#1619). The existing
LICENSE -> ../../../LICENSE symlinks in all cmd/*/kodata/ directories
resolve to the repo root, which ko now rejects when tarring for any
non-kind registry (including CI).

Replace the symlinks with actual copies of the LICENSE file.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
ko v0.19.0 introduced two breaking changes:
1. Strict kodata symlink enforcement (ko-build/ko#1619)
2. A YAML encoder error when a label selector filters all documents
   in a file (fixed in ko-build/ko fix-empty-docnodes-encoder-close)

Pin to v0.18.1 as a temporary workaround until ko releases a fixed
version. The kodata symlinks are also fixed in this branch.

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Jul 2, 2026
@tekton-robot tekton-robot requested review from abayer and afrittoli July 2, 2026 21:24
@tekton-robot tekton-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Jul 2, 2026
@vdemeester

Copy link
Copy Markdown
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 2, 2026
@vdemeester

Copy link
Copy Markdown
Member

/retest

@vdemeester

Copy link
Copy Markdown
Member

/approve

@tekton-robot

Copy link
Copy Markdown
Collaborator Author

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

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

The pull request process is described here

Details 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 Jul 3, 2026
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. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants