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

Update releases.json #34

Closed
stevieb9 opened this issue Jul 19, 2023 · 4 comments
Closed

Update releases.json #34

stevieb9 opened this issue Jul 19, 2023 · 4 comments
Labels

Comments

@stevieb9
Copy link
Contributor

I'd like to incorporate the new versions in berrybrew, but to do so, the releases.json file must be updated.

It appears as though it's a relatively trivial task to get this done, but it seems as though I'd need to have all the zip files locally (c:/strawberry_build/output).

Is there an easy way that I could mirror the list of releases? If so, I'll try my hand at getting the release list files updated. If not, could somebody else please do so?

@shawnlaffan
Copy link
Contributor

Are you grabbing it from the website or the github repo?

The website is still a work in progress as permissions are not yet in hand. See discussion under StrawberryPerl/Perl-Dist-Strawberry#114

If you are using the repo then then it should be pretty straightforward and the file just needs the 5.36.1.1 and 5.38.0.1 entries to be added, pointing to the GH release URLs under https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/tag/SP_5380_5361

A PR would be great if you are able to do so.

@stevieb9
Copy link
Contributor Author

Tomorrow, I'll update the files in the repo, test them, and create a PR. I'll also follow and monitor the website issue. I'll then have berrybrew use the repo releases.json file by default instead of the Strawberry site (at least for now).

@stevieb9
Copy link
Contributor Author

I have done this, and created a PR.

Once this is merged, berrybrew will be able to see and install the new versions. I won't be able to provide the full directions until the PR is merged in, but will do so thereafter.

I have mostly modified the generation of the releases.json file, so I'll monitor for new releases, and create a new PR each time a new one is available (unless I could be given write access to the repo, then I could fully automate it).

@shawnlaffan
Copy link
Contributor

I think this is closable?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants