-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
chore(release): Bump to version 0.5.3 (resync) #6436
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
Conversation
…ctDir` if it is empty (#6092) Co-authored-by: Hsiao-nan Cheung <[email protected]>
Co-authored-by: Hsiao-nan Cheung <[email protected]>
Signed-off-by: Chawye Hsu <[email protected]>
…6327) Co-authored-by: Hsiao-nan Cheung <[email protected]>
* global arg * changelog
* first step * Revert "first step" This reverts commit c5907c3. * refactor(Get-Manifest): Select actual source for installed manifest * rework sub-commands, `scoop-depends` is NOT working at this stage * URI manifest * opt * deprecated manifest * source of manifests * source of manifest pt2 - Mark URI(path/URL/UNC/etc.) query as standalone manifest - Drop `installed` and `available update` items for [query] and [installed] are different sources. * remove variable preventing I forget it * scoop-info: fix source of manifest on bucket * fix `scoop-depends` * Fix Standalone and Source detection * fix global install * Fix scoop-cat, scoop-home - Query for remote manifest * scoop-list: info +deprecated * manifest: Fix first selected manifest * gramma.. * Fix 61b3259 * length
* fix(scoop-depends-tests): Mocking `USE_EXTERNAL_7ZIP` as $false to avoding error when it is $true * CHANGELOG
* feat(autoupdate): predefined hash case for GitHub - Remove `sha256:` prefix in `format_hash()` - Add GitHub support in `get_hash_for_app()` Close #6381 * doc(chglog): GitHub auto hash update * fix(autoupdate): remove prefix only
* docs(CHANGELOG): Update to 0.5.3 * 6416
|
Okay, we must have a UGLY git log. |
#6435 introduced conflicts, making the situation more complicated.. it should have been committed after the sync. 😅 |
|
Yeah, I found it AFTER merged the PR, sadly... |
|
Please take a look for #6437, it just grabs that squash commit from master and an empty commit. Sync should be done when 0.5.4 release, right? |
|
It looks like #6437 would be better for our git log? We could merge master to develop then merge develop to master. |
|
I've merged master into develop, and after this PR, develop should be sync with master again, that's all done. |
|
@ScoopInstaller/maintainers Plan to going on today, so anyone could approve this PR? |
Approved. Hopefully everything will be fine. |
|
All done, now develop is synced with master, and we could start v0.5.4 now. |
|
Appreciate work and communication you guys made. |
|
#6438 may require our attention |
Description
Resync with
developbranch w/ a hotfix.Motivation and Context
Relates to #6434
How Has This Been Tested?
Checklist:
developbranch.