tektoncd / tektoncd/operator

bug(chart): mismatch between tekton-operator-0.80.0.tgz artifact content and git tag

Open
#3,827 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/bug
Dominant language
Go
Stars
608
Forks
263
Avg merge
1d 3h
Merged PRs (30d)
125

Description

Summary

There is a mismatch between the published Helm chart release artifact (tekton-operator-0.80.0.tgz) and the source code at Git tag tekton-operator-0.80.0.

The chart package contains changes from commit 0f90822d4 (and potentially others), which occurs after tag commit ca2b95e.

Expected Behavior

The published .tgz release asset should deterministically match the source tree at the tekton-operator-0.80.0 Git tag.

Actual Behavior

The contents of tekton-operator-0.80.0.tgz include commits beyond ca2b95e.

Given that tag v0.80.0 was previously re-pointed from ca2b95e to ffdc96b, it appears tekton-operator-0.80.0 may not have been moved in sync, or the release archive was packaged from a different commit reference.

Steps to Reproduce
  1. Download the release chart archive from the v0.80.0 release page:
wget https://github.com/tektoncd/operator/releases/download/tekton-operator-0.80.0/tekton-operator-0.80.0.tgz
tar -xzf tekton-operator-0.80.0.tgz
  1. Checkout tag tekton-operator-0.80.0 from the repository:
git checkout tags/tekton-operator-0.80.0
  1. Diff the extracted chart against the repository tree at tag tekton-operator-0.80.0.
  2. Note that commit 0f90822d4 (which is ahead of ca2b95e) is present inside the packaged chart.
Environment / Release Details
  • Release / Tag: tekton-operator-0.80.0
  • Asset Name: tekton-operator-0.80.0.tgz
  • Tag Commit: ca2b95e
  • Main Release Tag Commit (v0.80.0): ffdc96b
Additional Context / Request

Could the maintainers please confirm the exact commit reference used to build tekton-operator-0.80.0.tgz and ensure the tekton-operator-0.80.0 Git tag is updated or aligned accordingly?

Contributor guide

Open the contributing guide

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

Download tekton-operator-0.80.0.tgz from the v0.80.0 release page, extract it, and compare the chart with the repository at tag tekton-operator-0.80.0. Trace the referenced commits ca2b95e, ffdc96b, and 0f90822d4 to identify the build reference; done means the release asset deterministically matches the intended tag.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, helm
Domain
release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.