8000 Prepare to release a PATCH version of Rush · strogo/rushstack@6f44a98 · GitHub
[go: up one dir, main page]

Skip to content

Commit 6f44a98

Browse files
committed
Prepare to release a PATCH version of Rush
1 parent d4cb01d commit 6f44a98

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

common/changes/@microsoft/rush/dmyers-log-cache-key_2023-10-16-21-38.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"changes": [
33
{
44
"packageName": "@microsoft/rush",
5-
"comment": "Log cache key in `--verbose` mode when the cache is successfully read from or written to.",
5+
"comment": "Log the cache key in `--verbose` mode when the cache is successfully read from or written to.",
66
"type": "none"
77
}
88
],

common/changes/@microsoft/rush/jiawen-fix-color_2023-10-09-21-33.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"changes": [
33
{
44
"packageName": "@microsoft/rush",
5-
"comment": "Improve color logic when invoking package managers' install ",
5+
"comment": "Fix an issue where console colors were sometimes not enabled correctly during \"rush instal\"",
66
"type": "none"
77
}
88
],

common/changes/@microsoft/rush/main_2023-10-16-22-02.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
"changes": [
33
{
44
"packageName": "@microsoft/rush",
5-
"comment": "Fix an issue where running `rush update-cloud-credentials --interactive` in a repo configured to use the `http` build cache with a tokenHandler script provided would run the script in the console's CWD instead of in the repo root. If the tokenHandler script refered to a script in the repo (for example `node common/scripts/cache-auth.js`) and the user's CWD was inside a project folder, the script would not be found.",
5+
"comment": "Fix an issue where running `rush update-cloud-credentials --interactive` sometimes used the wrong working directory when invoked in a repo configured to use the `http` build cache provider (GitHub #4396)",
66
"type": "none"
77
}
88
],

0 commit comments

Comments
 (0)
0