New version: Beeper.Beeper version 3.102.10
Checklist for Pull Requests
- [x] Have you signed the Contributor License Agreement?
- [ ] Is there a linked Issue?
Manifests
- [x] Have you checked that there aren't other open pull requests for the same manifest update/change?
- [x] This PR only modifies one (1) manifest
- [x] Have you validated your manifest locally with
winget validate --manifest <path>? - [ ] Have you tested your manifest locally with
winget install --manifest <path>? - [x] Does your manifest conform to the 1.6 schema?
Note: <path> is the name of the directory containing the manifest you're submitting.
Microsoft Reviewers: Open in CodeFlow
/AzurePipelines run
Azure Pipelines successfully started running 1 pipeline(s).
Hi @SpecterShell,
I couldn't find a download link in the PackageUrl, and instead found "Join the waitlist" links. Has this package been officially released yet?
/AzurePipelines run
Azure Pipelines successfully started running 1 pipeline(s).
Hi @SpecterShell,
I couldn't find a download link in the
PackageUrl, and instead found "Join the waitlist" links. Has this package been officially released yet?
https://www.beeper.com/download which is at the bottom of the PublisherUrl. I have updated the PackageUrl accordingly.
The InstallerUrl is from https://download.todesktop.com/2003241lzgn20jd/latest.yml, which can be found in <INSTALLDIR>\resources\app-update.yaml
@stephengillie
Thanks for updating the PackageUrl.
The
InstallerUrlis from https://download.todesktop.com/2003241lzgn20jd/latest.yml, which can be found in<INSTALLDIR>\resources\app-update.yaml
The upgrade location for this application can be found in a YAML file of a previous version? I'm guessing this application has an upgrade check, and this is where the application records the upgrade's location. This sort of data isn't easy to record in the PackageUrl, to navigate between them.
Thanks for updating the
PackageUrl.The
InstallerUrlis from download.todesktop.com/2003241lzgn20jd/latest.yml, which can be found in<INSTALLDIR>\resources\app-update.yamlThe upgrade location for this application can be found in a YAML file of a previous version? I'm guessing this application has an upgrade check, and this is where the application records the upgrade's location. This sort of data isn't easy to record in the
PackageUrl, to navigate between them.
Yeah, the same file can also be found in the installer from the PackageUrl, and is usually consistent across the versions.
Many other (electron-based) packages are using the same methodology for upgrading, including Anydo.Anydo, JetBrains.Space and LukiLabs.Craft.
/AzurePipelines run
Azure Pipelines successfully started running 1 pipeline(s).
/AzurePipelines run
Azure Pipelines successfully started running 1 pipeline(s).
Verify:
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.