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

Support Release metadata in pgxn_spec #68

Closed
theory opened this issue Sep 12, 2024 · 1 comment · Fixed by pgxn/meta#24, pgxn/meta#25, pgxn/meta#26, pgxn/meta#27 or pgxn/meta#28
Closed

Support Release metadata in pgxn_spec #68

theory opened this issue Sep 12, 2024 · 1 comment · Fixed by pgxn/meta#24, pgxn/meta#25, pgxn/meta#26, pgxn/meta#27 or pgxn/meta#28
Assignees
Labels
client Work on or for the benefit of a PGXN CLI metadata Changes to the PGXN Meta spec or libraries

Comments

@theory
Copy link
Member

theory commented Sep 12, 2024

When a distribution is released, PGXN Manager adds three fields to the META.json file for its API, so that clients can validate downloads. Those fields are:

  • user: The PGXN username for the user who released the distribution to PGXN.
  • date: The timestamp for when the release was made.
  • sha1: The SHA-1 hash digest for the release, in hex.

In order for the CLI to be able to validate a download, add support for this data to pgxn/meta as follows:

  1. Add a v1 JSON schema that validates these fields.
  2. Add a v2 JSON schema that augments the distribution metadata with a new object that contains more/better release metadata, including a URL and flexible SHA representation.
  3. Add a struct to support this new field, along with the appropriate accessors.
@theory theory added client Work on or for the benefit of a PGXN CLI metadata Changes to the PGXN Meta spec or libraries labels Sep 12, 2024
@theory theory added this to the 🗃️ Metadata milestone Sep 12, 2024
@theory theory self-assigned this Sep 12, 2024
@theory theory added this to PGXN v2 Sep 12, 2024
@github-project-automation github-project-automation bot moved this to Backlog in PGXN v2 Sep 12, 2024
@theory theory moved this from Backlog to In progress in PGXN v2 Sep 12, 2024
@theory theory linked a pull request Sep 12, 2024 that will close this issue
@theory theory removed a link to a pull request Sep 12, 2024
@github-project-automation github-project-automation bot moved this from In progress to Done in PGXN v2 Sep 16, 2024
@theory theory reopened this Sep 16, 2024
@github-project-automation github-project-automation bot moved this from Done to Ready in PGXN v2 Sep 16, 2024
@github-project-automation github-project-automation bot moved this from In review to Done in PGXN v2 Sep 23, 2024
@theory theory reopened this Oct 4, 2024
@github-project-automation github-project-automation bot moved this from Done to Ready in PGXN v2 Oct 4, 2024
@theory
Copy link
Member Author

theory commented Oct 8, 2024

Since

You may only link 10 pull requests to this issue across all repositories.

Adding these here:

@github-project-automation github-project-automation bot moved this from Ready to Done in PGXN v2 Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment