Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add(new): pvc-autoresizer package non-fips #48359

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

YashPimple
Copy link
Contributor

Fixes:

Related:

Pre-review Checklist

For new package PRs only

  • This PR is marked as fixing a pre-existing package request bug
    • Alternatively, the PR is marked as related to a pre-existing package request bug, such as a dependency
  • REQUIRED - The package is available under an OSI-approved or FSF-approved license
  • REQUIRED - The version of the package is still receiving security updates
  • This PR links to the upstream project's support policy (e.g. endoflife.date)

For new version streams

  • The upstream project actually supports multiple concurrent versions.
  • Any subpackages include the version string in their package name (e.g. name: ${{package.name}}-compat)
  • The package (and subpackages) provides: logical unversioned forms of the package (e.g. nodejs, nodejs-lts)
  • If non-streamed package names no longer built, open PR to withdraw them (see WITHDRAWING PACKAGES)

For package updates (renames) in the base images

When updating packages part of base images (i.e. cgr.dev/chainguard/wolfi-base or ghcr.io/wolfi-dev/sdk)

  • REQUIRED cgr.dev/chainguard/wolfi-base and ghcr.io/wolfi-dev/sdk images successfully build
  • REQUIRED cgr.dev/chainguard/wolfi-base and ghcr.io/wolfi-dev/sdk contain no obsolete (no longer built) packages
  • Upon launch, does apk upgrade --latest successfully upgrades packages or performs no actions

For security-related PRs

  • The security fix is recorded in the advisories repo

For version bump PRs

  • The epoch field is reset to 0

For PRs that add patches

  • Patch source is documented

Signed-off-by: YashPimple <[email protected]>
@YashPimple YashPimple added the approved-to-run A repo member has approved this external contribution label Mar 27, 2025
Copy link
Contributor

octo-sts bot commented Mar 27, 2025

⚠️ EXPERIMENTAL

Please use 👍 or 👎 on this comment to indicate if you agree or disagree with the recommendation.

To provide more detailed feedback please comment on the recommendation prefixed with /ai-verify:

e.g. /ai-verify partially helpful but I also added bash to the build environment

Gen AI suggestions to solve the build error:

Let me help analyze and fix this build error.

• Detected Error:

Error: failed to run update. Error: failed to run 'go get': exit status 1 with output: go: golang.org/x/[email protected]: invalid version: unknown revision 0.36.0

• Error Category: Dependency

• Failure Point:
The go/bump step attempting to update golang.org/x/net dependency

• Root Cause Analysis:
The error indicates that version 0.36.0 of golang.org/x/net doesn't exist. This is likely because we're trying to use a version that hasn't been released yet or the version format is incorrect for this Go module.

• Suggested Fix:
Modify the go/bump step to use the latest known good version of golang.org/x/net:

  - uses: go/bump
    with:
      deps: |-
        golang.org/x/[email protected]
        golang.org/x/[email protected]

• Explanation:

  • Go modules like golang.org/x/net use versioning with the 'v' prefix
  • The versions suggested above are known stable releases
  • The error occurs because we're trying to use version numbers that don't exist in the upstream repository

• Additional Notes:

  • Always verify Go dependency versions against the official repo before updating
  • For x/net and x/oauth2, versions typically follow Go releases
  • Consider using go list -m -versions golang.org/x/net to check available versions

• References:

@octo-sts octo-sts bot added the ai/skip-comment Stop AI from commenting on PR label Mar 27, 2025
Signed-off-by: YashPimple <[email protected]>
Signed-off-by: YashPimple <[email protected]>
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Mar 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ai/skip-comment Stop AI from commenting on PR approved-to-run A repo member has approved this external contribution bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant