Merge remote-tracking branch 'origin/1.x' into dev

This commit is contained in:
Lucas Nogueira 2023-06-17 11:02:14 -03:00
commit 1e9c463d12
No known key found for this signature in database
GPG Key ID: FFEA6C72E73482F1
16 changed files with 30 additions and 19 deletions

View File

@ -7,6 +7,7 @@
"bug": "Bug Fixes",
"pref": "Performance Improvements",
"changes": "What's Changed",
"sec": "Security fixes",
"deps": "Dependencies"
},
"defaultChangeTag": "changes",

View File

@ -8,7 +8,7 @@ on:
push:
branches:
- dev
- next
- 1.x
workflow_dispatch:
env:

View File

@ -25,7 +25,7 @@ jobs:
list-files: shell
filters: |
changes:
- '.changes/*.md'
- added|modified: '.changes/*.md'
- name: check
run: node ./.scripts/ci/check-change-tags.js ${{ steps.filter.outputs.changes_files }}

View File

@ -7,7 +7,7 @@ name: covector version or publish
on:
push:
branches:
- dev
- 1.x
jobs:
run-integration-tests:
@ -99,8 +99,8 @@ jobs:
uses: tauri-apps/create-pull-request@v3
with:
token: ${{ secrets.GITHUB_TOKEN }}
branch: release/version-updates
title: Apply Version Updates From Current Changes
branch: release/version-updates-v1
title: Apply Version Updates From Current Changes (v1)
commit-message: 'apply version updates'
labels: 'version updates'
body: ${{ steps.covector.outputs.change }}

View File

@ -8,7 +8,7 @@ on:
push:
branches:
- dev
- next
- 1.x
pull_request:
paths:
- '.github/workflows/lint-cli.yml'

View File

@ -8,7 +8,7 @@ on:
push:
branches:
- dev
- next
- 1.x
pull_request:
paths:
- '.github/workflows/lint-core.yml'

View File

@ -8,7 +8,7 @@ on:
push:
branches:
- dev
- next
- 1.x
pull_request:
paths:
- '.github/workflows/test-cli-js.yml'

View File

@ -8,7 +8,7 @@ on:
push:
branches:
- dev
- next
- 1.x
pull_request:
paths:
- '.github/workflows/test-cli-rs.yml'

View File

@ -8,7 +8,7 @@ on:
push:
branches:
- dev
- next
- 1.x
pull_request:
paths:
- '.github/workflows/test-core.yml'

View File

@ -8,7 +8,7 @@ on:
push:
branches:
- dev
- next
- 1.x
pull_request:
paths:
- '.github/workflows/test-bundler.yml'

View File

@ -8,7 +8,7 @@ on:
push:
branches:
- dev
- next
- 1.x
env:
RUST_BACKTRACE: 1

View File

@ -1935,7 +1935,7 @@
}
},
"requireLiteralLeadingDot": {
"description": "Whether or not paths that contain components that start with a `.` will require that `.` appears literally in the pattern; `*`, `?`, `**`, or `[...]` will not match. This is useful because such files are conventionally considered hidden on Unix systems and it might be desirable to skip them when listing files.\n\nDefaults to `false` on Unix systems and `true` on Windows",
"description": "Whether or not paths that contain components that start with a `.` will require that `.` appears literally in the pattern; `*`, `?`, `**`, or `[...]` will not match. This is useful because such files are conventionally considered hidden on Unix systems and it might be desirable to skip them when listing files.\n\nDefaults to `true` on Unix systems and `false` on Windows",
"type": [
"boolean",
"null"

View File

@ -1195,7 +1195,7 @@ pub enum FsScope {
/// conventionally considered hidden on Unix systems and it might be
/// desirable to skip them when listing files.
///
/// Defaults to `false` on Unix systems and `true` on Windows
/// Defaults to `true` on Unix systems and `false` on Windows
// dotfiles are not supposed to be exposed by default on unix
#[serde(alias = "require-literal-leading-dot")]
require_literal_leading_dot: Option<bool>,

View File

@ -140,6 +140,16 @@
- Export types required by the `mobile_entry_point` macro.
- [98904863](https://www.github.com/tauri-apps/tauri/commit/9890486321c9c79ccfb7c547fafee85b5c3ffa71) feat(core): add `mobile_entry_point` macro ([#4983](https://www.github.com/tauri-apps/tauri/pull/4983)) on 2022-08-21
## \[1.4.1]
### Bug Fixes
- [`6afd3472`](https://www.github.com/tauri-apps/tauri/commit/6afd34727f153b32dbc568d169dbb17fb8dc3539)([#6680](https://www.github.com/tauri-apps/tauri/pull/6680)) Revert [#6680](https://github.com/tauri-apps/tauri/pull/6680) which added a default sound for notifications on Windows. This introduced inconsistency with other platforms that has silent notifications by default. In the upcoming releases, we will add support for modifying the notification sound across all platforms.
### Security fixes
- [`066c09a6`](https://www.github.com/tauri-apps/tauri/commit/066c09a6ea06f42f550d090715e06beb65cd5564)([#7227](https://www.github.com/tauri-apps/tauri/pull/7227)) Fix regression in `1.4` where the default behavior of the file system scope was changed to allow reading hidden files and directories by default.
## \[1.4.0]
### New Features

View File

@ -108,9 +108,9 @@ impl Scope {
} => *require,
// dotfiles are not supposed to be exposed by default on unix
#[cfg(unix)]
_ => false,
#[cfg(windows)]
_ => true,
#[cfg(windows)]
_ => false,
};
Ok(Self {
@ -281,9 +281,9 @@ mod tests {
require_literal_separator: true,
// dotfiles are not supposed to be exposed by default on unix
#[cfg(unix)]
require_literal_leading_dot: false,
#[cfg(windows)]
require_literal_leading_dot: true,
#[cfg(windows)]
require_literal_leading_dot: false,
..Default::default()
},
}

View File

@ -1935,7 +1935,7 @@
}
},
"requireLiteralLeadingDot": {
"description": "Whether or not paths that contain components that start with a `.` will require that `.` appears literally in the pattern; `*`, `?`, `**`, or `[...]` will not match. This is useful because such files are conventionally considered hidden on Unix systems and it might be desirable to skip them when listing files.\n\nDefaults to `false` on Unix systems and `true` on Windows",
"description": "Whether or not paths that contain components that start with a `.` will require that `.` appears literally in the pattern; `*`, `?`, `**`, or `[...]` will not match. This is useful because such files are conventionally considered hidden on Unix systems and it might be desirable to skip them when listing files.\n\nDefaults to `true` on Unix systems and `false` on Windows",
"type": [
"boolean",
"null"