d09180fd89
* reorder packages that core is published last * general ledger comment, not just npm * we do want to create releases * leading ! does not seem to negate * dump a bunch of info to debug |
||
|---|---|---|
| .. | ||
| appimage-container.md | ||
| bundler-output.md | ||
| config.json | ||
| fix-fs-api.md | ||
| js-prompt.md | ||
| notificaiton-fix.md | ||
| notification-permission-regression.md | ||
| plugin-system.md | ||
| promisified-leak.md | ||
| readme.md | ||
| refactor-whitelist.md | ||
| tauri-cli-admin.md | ||
| tauri-info-outdated.md | ||
| tauri-init.md | ||
| tauri-package-json.md | ||
| tauri-webview.md | ||
| tauri.js-dependency-manager.md | ||
| tauri.js-install-on-init.md | ||
| taurijs_move_api_types_into_api.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 it represents the overall change for our sanity.
When you select the version bump required, you do not need to consider depedencies. 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:
---
"tauri.js": patch
"tauri": minor
---
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).