Skip to content

feat: allow per-extension license metadata#111

Open
gbartolini wants to merge 2 commits intomainfrom
dev/110
Open

feat: allow per-extension license metadata#111
gbartolini wants to merge 2 commits intomainfrom
dev/110

Conversation

@gbartolini
Copy link
Contributor

This change introduces a licenses field to the metadata schema, allowing each extension to define its own SPDX license identifier. The docker-bake.hcl has been updated to use this metadata for OCI labels and annotations instead of a hardcoded "Apache-2.0" string.

This enables proper legal transparency for extensions with different, yet compatible, licensing requirements, such as PostGIS (GPL-2.0-only).

Changes:

  • Added licenses field to metadata.hcl template
  • Updated docker-bake.hcl to reference ${metadata.licenses}
  • Updated metadata.hcl for the existing extensions

Closes #110

@gbartolini gbartolini requested review from a team and NiccoloFei as code owners February 15, 2026 23:34
This change introduces a `licenses` field to the metadata schema, allowing each
extension to define its own SPDX license identifier. The `docker-bake.hcl` has
been updated to use this metadata for OCI labels and annotations instead of a
hardcoded "Apache-2.0" string.

This enables proper legal transparency for extensions with different, yet
compatible, licensing requirements, such as PostGIS (`GPL-2.0-only`).

Changes:

- Added `licenses` field to metadata.hcl template
- Updated docker-bake.hcl to reference `${metadata.licenses}`
- Updated `metadata.hcl` for the existing extensions

Closes #110

Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enable customisation of the licenses annotation and label

1 participant