Skip to content

Investigate reducing the number of required files, so more modules can be attached to a GitHub release #17

Description

@aSemy

GitHub Releases have a limit of 1000 attached assets.

https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases#storage-and-bandwidth-quotas

Kotlin Multiplatform projects could quickly reach this limit.

Argh already takes steps to limit the amount of attached files, e.g. only publish .sha256 checksums. However,

Initial thoughts:

  • Fetch checksums via GitHub API. Possible in Maven, but not possible in Gradle Create custom ArtifactRepository type gradle/gradle#27449.
  • Don't publish .pom files, and update the Maven resolver to parse .module files.
  • Bundle all files for a subproject into a single archive. Use Gradle artifact transformers to extract the data for each module. Implement something similar in the Maven resolver. Must be careful of the 2GB file size limit.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions