Releases: facebook/sapling
Releases · facebook/sapling
Release list
0.2.20230330-193452-h69692651
This release includes fixes in various areas:
- @vegerot fixed a crash on macOS when the user belongs to more than 16 unix groups (#573).
- @steveluscher improved
githelpto properly include--dirsforcleancommand (#575). - @steveluscher improved Ubuntu build by including build dependencies (#576, #577).
- Ctrl+C is now properly handled (1a697a2).
0.2.20230228-144002-h9440b05e
This release mainly brings better file move detection as well as various improvements to the sl pr submit command
- Added file moves detection for sl diff.
- @discentem added a config option to disable the ReviewStack message in PRs created by
sl pr submit(#427). The ReviewStack message is auto disabled for single-commit stack. - Fixed "mark landed PRs" hook to work when
slnot in PATH (71d6e67) - Fixed
sl pr submitto not try to update closed PRs (5a354f7) - Fixed
sl pr submitto use "overlapping" PR strategy by default (a050359) - Fix
sl pr submitcrash using non-placeholder issue approach (18a1987) - @vegerot added and improved shell completion and prompt (#369 #349 #348).
- @vegerot added support for
sl init --giton a non-empty directory. - Fixed not being able to launch
sl webjust after building withmake oss.
0.2.20230124-180750-hf8cd450a
This release focuses on bug fixes and improvements around the pr and ghstack commands.
- Fixed an issue where
sl pr listdid not work correctly in combination withchg(a1187e8). - @discentem (BK) Updated
sl pr pullto throw an appropriate error if no args were specified (#357). - Reverted the behavior introduced in the previous release that introduced the practice of using placeholder issues when creating GitHub pull requests. While this approach made it possible to create pull requests in parallel and had desirable guarantees with respect to PR numbers and branch names, it turned out to have a number of downsides that outweighed the benefits, as explained in 7ce516d .
- @discentem (BK) Fixed a bug where
sl clonesilently failed for some repositories (#375) with (#386). - Added a PR revset (4720a2e). Now commands such as
sl goto pr123,sl log -r PR456should work, even without having to manually download some pull request. Using sl pr pull is still necessary, however, if one wants to get the most recent version of some PR. - Fix
sl ghstack landto properly rebase, avoiding spurious “non-fast forward” push errors (ebbe7d8), resolving #333 .
0.2.20230124-124516-h352feeef
mirror: Log less and make concurrency customisable Summary: Slices were very noisy, so I made them log less. Plus now you can specify the concurrency of the command via CLI args. I tweaked it and saw no improvements though :( Reviewed By: markbt Differential Revision: D42683915 fbshipit-source-id: 5930a44c6a24fd48560512dd83a630c283c9a351
0.2.20221222-152408-ha6a66d09
This release focuses on correctness issues around handling submodules as well as various usability/workflow improvements.
- We made a number of improvements to working in repos with submodules:
- Rebasing past an update to a submodule no longer adds the submodule change to the bottom of the stack that was rebased: 2f0f0fd
- Rebasing a stack that contains a submodule change will preserve the change in the destination if the destination does not change the submodules: 1f5424d
- Rebasing a stack with a conflicting submodule change no longer crashes: 2b94b6f
- Improvements to the
sl prcommand:- You must now specify
sl pr submitexplicitly:submitis no longer the default subcommand forsl pr, butscan be used as an alias forsubmit: 56b5e3e - The
sl pr submitcommand now supports a--draftflag: 6e9c3d7 - New
sl pr pullsubcommand: if you usesl pr submitto create a stack of pull requests, now you can usesl pr pullto import the stack back into your working copy: d09d598 - New
sl pr listsubcommand that mirrors the functionality ofgh pr list: 8f0a657 - Experimental new command for creating stacks:
sl --config github.pr_workflow=single pr submit. See #302 and 166e264 for details. sl pr submitnow appends the stack information to the end of the pull request body instead of prepending it to the top: 8910d18- The branch name for a PR created by
sl pr submitis now guaranteed to match the PR number: e77e67b
- You must now specify
- Improvements to commands involving remote names and bookmarks:
- SCP-style URIs (such as
git@github.com:git/git-reference) are now supported for remote names: 67fa848 sl clone --git <URL> --updaterev <branch/commit>can now be used to clone a specific branch or commit: 9804c66sl rebase -bwas reworked for better selecting branching points by avoiding public commits (reverse rebase now works): 96b767esl bookmark --remotecan be used to list remote branches. Further,sl bookmark --remote-path myfork --remote tagswill list tags from remotemyfork:- e8f57d7
- SCP-style URIs (such as
- It is now possible to specify the Git committer for newly created commit objects by specifying the
git.committerconfig option when running a command. For example,sl --config git.committer="User <user@example.com>" amendwould update the committer for the current commit toUser <user@example.com>. Though note that ifgit.committeris not set, the value defaults to theui.usernameconfig. This means thatsl metaedit --user IDENTITYwill not update the committer toIDENTITYif thegit.committerconfig is not set, butsl metaedit --config ui.username=IDENTITY --user IDENTITYwould. See 7f88efd for details. - Removed a dependency on
gdbmin the Python code, that was causing crashes for some users: cfbb6a2
0.1.20221213-150011-h9b0acf12
Updating submodules Summary: GitHub commits: https://github.com/facebook/fbthrift/commit/937d00c39b2862f1917ee792e9f5fff406d4e80d https://github.com/facebook/litho/commit/e0bb6f15264ddfd6e447c3583a7696e3236c78d3 https://github.com/facebook/proxygen/commit/0c5d06fc785a49c64a701015199b00cc1b8b8e23 https://github.com/facebookincubator/velox/commit/b06bf84f4df7ea21c1c54d1edb5e253ac765b3a5 Reviewed By: yns88 fbshipit-source-id: 8bb9476d603174fde43cfa7b79c6d72ca61a6f10
0.1.20221212-142634-r7ae28228
prepare Sapling VS Code extension for release (v0.1.7) Summary: This fixes a fairly annoying issue in the VS Code extension. Now outstanding issues fall more in the "feature request" than "bug" category. Reviewed By: ndmitchell Differential Revision: D41976202 fbshipit-source-id: 31e6a38df50d90e4e0df2b21450f9175ba57f680
0.1.20221208-212056-r520df27a
Updating submodules Summary: GitHub commits: https://github.com/facebook/fbthrift/commit/423efb1c2bc6f0f45d738bf2fe288d49d0828d9e https://github.com/facebook/proxygen/commit/0883fee9c8eb44173127d3469fe9fc221ff56a0d https://github.com/facebook/watchman/commit/c71641be98b35294be6586a7b943f8d76103b8a3 https://github.com/facebookincubator/katran/commit/a80b782e48b45cd2ca5f8233ff8af786b911fd4f Reviewed By: jailby fbshipit-source-id: 18cd08bd863e1907ebc799dd9cab1b42fff47d50
0.1.20221208-111736-r4b499bce
service: only allow takeover if all mounts are initialized Summary: The most common crash on macOS is when a graceful restart is performed while a mount is ongoing. In this case, an EDEN_BUG is raised in EdenFS leading to EdenFS to crash and restart. As a very easy solution, let's check prior to starting graceful restart if there are any ongoing mounts, and if so, just abort the graceful restart. Note that there is still a potential race if a mount occurs right after this check, but that should be significantly more rare and unlikely to happen in practice. Reviewed By: kmancini Differential Revision: D41640271 fbshipit-source-id: c0fd0cc0305cbcdd941aa0e2e422706af799d5b3
0.1.20221201-095354-r360873f1
Updating submodules Summary: GitHub commits: https://github.com/facebook/fbthrift/commit/053bb0dee96cdbe5cd008b42e155514f07d13f24 Reviewed By: apiri fbshipit-source-id: b594498c18cf0727143603859f3bb463cb2fac6f