This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
astro-org@2.0.1
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Updated dependencies [
e71a8a8
]:orgast-util-to-string@1.0.1
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
orgast-util-visit-ids@1.0.1
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
@uniorgjs/orgx@1.0.5
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Updated dependencies [
e71a8a8
]:rollup-plugin-orgx@1.0.1
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Updated dependencies [
e71a8a8
]:uniorg@1.1.1
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
uniorg-attach@1.0.1
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
uniorg-extract-keywords@1.0.1
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
uniorg-parse@2.1.1
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
uniorg-rehype@1.1.1
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
uniorg-slug@1.0.1
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Updated dependencies [
e71a8a8
]:uniorg-stringify@1.1.1
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
example@1.0.2
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Updated dependencies [
e71a8a8
]:extract-keywords-example@1.0.2
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Updated dependencies [
e71a8a8
]:blog-starter@1.0.2
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Updated dependencies [
e71a8a8
]:org-braindump@1.0.2
Patch Changes
#94
e71a8a8
Thanks @rasendubi! - Upgrade dependencies.Most notably, this upgrades vfile version. This does not change the code and the old code should continue working. But it might break the types so you might need to upgrade vfile version as well (if you're manipulating vfiles directly).
Updated dependencies [
e71a8a8
]: