How to associate a package asset with a project release (as a Release Asset)?

[eric-creekside]

Select Topic Area

General

Body

In our organization we use repository Releases and Packages (Maven packages, if it matters). One particular repo produces 2 different Packages; a step in our CI/CD build script uploads the Package assets automatically.
For one particular Release, I see related Package assets associated with that Release as Assets, which is convenient. But it's just for that 1 release, no other releases include a Package as an asset. I'm quite sure I did not manually upload that Package as an Asset to the Release, so how is this accomplished?

[rajtilak-2020]

Hi,

It seems like you're encountering a situation where a package is automatically associated as an asset with a particular release in your repository, but not with others. This could be due to an automated process within your CI/CD pipeline that links the package to the release in a way that GitHub detects it as an asset.

Here are a few possibilities for why this might happen:

1. CI/CD Workflow Configuration:
   The build script might have specific steps that automatically associate the package with the release based on certain conditions (like version tags or release triggers). It's possible that the CI/CD pipeline is using the upload-release-asset action or a similar mechanism to attach the package as an asset to a release during the build process.

2. Package Publishing Configuration:
   If you are using Maven and GitHub Packages, there could be configuration within the Maven pom.xml or another configuration file that associates certain package versions with specific releases. This might be conditional or based on specific release criteria that only applied to that one particular release.

3. GitHub Actions or GitHub API:
   It's possible that an action or API call within your workflow is making the association automatically, and this might only trigger for certain releases (for example, based on the type of change or branch).

To investigate further, check your CI/CD pipeline configuration and see if there are any scripts or actions that could be automatically uploading or associating the package as an asset.

Hope that helps! Let me know if you need further clarification.

[eric-creekside]

I don't think any of those is the case. Some clarification:

• We use Jenkins to execute builds, not GitHub Actions (we use GitHub actions, but only for pre-merge PR builds, and those actions have no publish steps).
• Our builds are written in Gradle.
• The only publishing in build scripts is using the maven-publish plugin, with nothing GitHub specific other than the URL and credentials for our GitHub Packages repo.
• There is absolutely nothing in our build scripts related to GitHub Releases, generating releases in GitHub is a 100% manual process.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬