Startseite Erkunden Hilfe
Registrieren Anmelden
root
/
tauri-workspace
1
0
Fork 0
Dateien Issues 0 Pull-Requests 0 Wiki
Branch: feat/ci-ios-test
Branches Tags
tauri-workspace
/
.changes
Lucas Fernandes Nogueira f6f9192aa5 fix(core): Android compilation on Windows (#5658) vor 2 Jahren
..
build-android-env-vars.md 9890486321 feat(core): add `mobile_entry_point` macro (#4983) vor 3 Jahren
cli-android-build.md 4c9ea450c3 feat(cli): add `android build` command (#4999) vor 2 Jahren
cli-ios-build.md 403859d47e feat(cli): add `ios build` command (#5002) vor 2 Jahren
cli-mobile-dev.md 6f0615044d feat(cli): add `android dev` and `ios dev` commands (#4982) vor 3 Jahren
codegen-mobile-devurl.md 6f0615044d feat(cli): add `android dev` and `ios dev` commands (#4982) vor 3 Jahren
config.json 169d2434ff Merge remote-tracking branch 'origin/dev' into next vor 2 Jahren
default-tls-features.md f6f9192aa5 fix(core): Android compilation on Windows (#5658) vor 2 Jahren
dev-proxy.md 6f0615044d feat(cli): add `android dev` and `ios dev` commands (#4982) vor 3 Jahren
mobile-config.md b3a3afc7de feat(core): detect android and ios platform configuration files (#4997) vor 2 Jahren
mobile-entry-point-macro.md 9890486321 feat(core): add `mobile_entry_point` macro (#4983) vor 3 Jahren
mobile-init.md d44f67f7af feat: add `android init` and `ios init` commands (#4942) vor 3 Jahren
mobile-open.md a9c8e565c6 feat: add `android open` and `ios open` commands (#4946) vor 3 Jahren
mobile-webview-access.md 8ea87e9c9c feat(android): with_webview access for jni execution (#5148) vor 2 Jahren
readme.md a5861d8294 chore: add covector readme (#5255) vor 2 Jahren
refactor-setup.md b4622ea4d3 refactor(app): run setup and window creation when event loop is ready (#4914) vor 3 Jahren
tauri-mobile-entry-point.md 9890486321 feat(core): add `mobile_entry_point` macro (#4983) vor 3 Jahren

readme.md

Changes

via https://github.com/jbolda/covector

As you create PRs and make changes that require a version bump, please add a new markdown file in this folder. You do not note the version number, but rather the type of bump that you expect: major, minor, or patch. The filename is not important, as long as it is a .md, but we recommend that it represents the overall change for organizational purposes.

When you select the version bump required, you do not need to consider dependencies. Only note the package with the actual change, and any packages that depend on that package will be bumped automatically in the process.

Use the following format:

---
"package-a": patch
"package-b": patch
---

Change summary goes here

Summaries do not have a specific character limit, but are text only. These summaries are used within the (future implementation of) changelogs. They will give context to the change and also point back to the original PR if more details and context are needed.

Changes will be designated as a major, minor or patch as further described in semver.

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes,
  • MINOR version when you add functionality in a backwards compatible manner, and
  • PATCH version when you make backwards compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format, but will be discussed prior to usage (as extra steps will be necessary in consideration of merging and publishing).