Repository navigation
chore(release): version packages - #460
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 12, 2026 15:16
f8393c3 to
3d2bc14
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 main, this PR will be updated.
Releases
@office-kit/pptx@0.24.1
Patch Changes
getCorePropertiesreturnednull, andsetCorePropertiesadded a second core-properties part and relationship, for packages that store core properties somewhere other than/docProps/core.xml(e.g.package/services/metadata/core-properties/….psmdcp) (bug: core properties are looked up at /docProps/core.xml only; setCoreProperties then adds a second core-properties part #457). Core and extended properties are now found through the package's root relationships, as OPC specifies, sogetExtendedProperties/setExtendedPropertiesalso work whenapp.xmllives elsewhere. A/docProps/core.xmlpart that no relationship points at is no longer read as the core properties, and a core-properties relationship whose target escapes the package root (../…) now throws instead of being ignored.duplicateSlide,addSlideImageand other edits could save XML with an unboundr:(or other) prefix when the template declared that prefix on individual elements instead of the part root, so the saved file failed to load (bug: duplicateSlide / addSlideImage write an undeclared r: prefix, so the saved file can't be parsed #456). The writer now declares any prefix a new element or attribute uses that is not already in scope.