Skip to content
This repository has been archived by the owner on Sep 6, 2024. It is now read-only.

Update Jetpack Beta URL for latest release downloading #236

Open
oskosk opened this issue Jun 26, 2021 · 3 comments · May be fixed by #237
Open

Update Jetpack Beta URL for latest release downloading #236

oskosk opened this issue Jun 26, 2021 · 3 comments · May be fixed by #237
Labels

Comments

@oskosk
Copy link
Collaborator

oskosk commented Jun 26, 2021

The Jetpack Beta Tester Plugin started being developed on the Jetpack monorepo, so the former repo is no longer a valid source for getting a master copy and installing on JN

For now JN is carrying a manual change making it download

https://github.com/Automattic/jetpack-beta/releases/latest/download/jetpack-beta.zip

Update: Seems like the intention was for the jetpack-beta repository to have a full blown vendor directory but there was an oversight in the automation process that ships code form the Jetpack monorepo to the Jetpack Beta Tester repository..

Still, it may be best if Jurassic Ninja downloaded a latest release bundle instead of a master bundle so to allow developers to have unreleased work in master without compromising the latest official release of the Jetpack Beta Tester plugin

@oskosk oskosk added the bug label Jun 26, 2021
@brbrr
Copy link
Contributor

brbrr commented Jun 26, 2021

This PR should resolve the issue in current master: Automattic/jetpack#20187

@kraftbj
Copy link
Contributor

kraftbj commented Jun 26, 2021

I'd agree that we should run latest release instead of master, by default.

It would be nice to be able to indicate master from special ops so we can smoke test before tagging a new version.

@oskosk
Copy link
Collaborator Author

oskosk commented Jun 26, 2021

It would be nice to be able to indicate master from special ops so we can smoke test before tagging a new version.

good call!

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

Successfully merging a pull request may close this issue.

3 participants