chore: Bump uSync from 18.0.3 to 18.1.1 - #25
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
--- updated-dependencies: - dependency-name: uSync dependency-version: 18.1.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
Superseded by #28. |
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
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.
Updated uSync from 18.0.3 to 18.1.1.
Release notes
Sourced from uSync's releases.
18.1.1
Fixes
<Tabs>entry) not actually persisting that move on import — it took a second import to stick. (#1043)SaveBlueprintlike a normal single-item save. (#1035)Other
18.1.0
This is a minor update to uSync for Umbraco 18 — an opt-in import performance cache, a double-export fix for save-and-publish, several allocation/perf improvements ported from v17, and a move to the
Jumoo.Jsonpackage for JSON handling.uSync 18.1.0
Added
uSync:Settings:CacheImportState(defaultfalse). uSync normally decides whether an item has changed by loading it, serializing it, and hashing it — every item, every run. With this on, uSync remembers the hash of items it has already confirmed match, so unchanged items are skipped without a database lookup or re-serialize on the next run. The first run after enabling it is no faster than before; the benefit lands on the second run. Readdocs/perf/state-cache.mdbefore enabling it, especially the limitations section. (#1016)Message(used instead of uSync's generic cancel message) and, on the import/report ones,Force, so a subscriber can stand down when the user has asked for a forced import.Fixed
HandlerSettings.Clone()no longer dropsCreateCleanandFullFileOnDifference— handlers that set either value in their own block are now honoured.Jumoo.Json.Performance
internal/privateclasses are nowsealedso the JIT can devirtualize their calls. No behavioural changes. (#1019, #1020)HandlerDefaults. A handler's own settings block is layered over the set's defaults instead of replacing them wholesale, so it only needs to specify what it wants to change. (#1001)Jumoo.Jsonpackage, replacing uSync's own copy which had drifted behind it.uSync.Core.Extensions.JsonTextExtensionsstill works but is[Obsolete](removed in v20) — switch tousing Jumoo.Json;. NoteTryGetPropertyAsObject→TryGetPropertyAsJsonObject,GetPropertyAsObject→GetPropertyAsJsonObject, and missing/null values now returnnullinstead ofstring.Empty. (#1014, #1015)Jumoo.Json.Extender API
ISyncManagementServicegainsUnpackStreamAsync(Stream); the synchronousUnpackStream(Stream)is now obsolete (removed in v19). (#1005)Cleanup
ITemplate.MasterTemplateAliaswithLayoutTemplateAlias, and inlined the legacy{localLink:x}parsing Umbraco is removing in v18. No behavioural changes. (#1002, #1003, #1004)Full Changelog: KevinJump/uSync@v18.0.3...v18.1.0
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)