Skip to content

v0.5.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Oct 05:29
· 13 commits to main since this release
v0.5.0
cffa50f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Third stable release of the channel, and the first since 0.3.2 on NuGet.org / npmjs. The 0.5.0 line moves field
storage onto the Dignite.Abp.FlexFields kernel (field architecture v3), rebuilds the document permission core
on ABP's resource-based authorization (per-type grants, uploader ownership, Documents.ReadAll), tidies the
multi-stage event contract (DocumentTextExtractedEto, FieldsExtractedEto retired), replaces re-classify with a
re-parse from the original file, adds operator notifications and a per-tenant on/off feature, moves the MCP
server onto the shared Dignite.Abp.AspNetCore.Mcp endpoint (vault_extract_* tool names), and lands on
ABP Framework 10.7 / Angular 22. The granular per-preview history, with the migration for every breaking entry, is
retained in the 0.5.0-preview.* sections of CHANGELOG.md; this section lists only what changed after 0.5.0-preview.17.

As a 0.y.z release the exit contracts may still change — see CONTRIBUTING → Versioning and releases.
Upgrading from 0.3.x is breaking on the REST, EventBus, MCP, permission and Angular contracts (each entry marked
BREAKING below carries its migration) and needs the EF migrations of this line applied (--migrate-database).
A 0.3.x deployment that holds field values must run the field architecture v2 → v3 data migration first: it
ships only in 0.5.0-preview.1 / 0.5.0-preview.2, which were published to GitHub Packages, not to NuGet.org —
follow the runbook on one of those builds, verify it, and
only then move to 0.5.0. Skipping it loses every field value while the upgrade reports success (see 0.5.0-preview.4 in the CHANGELOG).
The Angular library is published as @dignite/ng.vault-extract; @dignite/vault-extract stops at 0.3.2.

Changed

  • abp-modules 10.7.0, the first stable release, on both sides (was 10.0.0-rc.29). Dignite.Abp.FlexFields.*,
    Dignite.Abp.AspNetCore.Mcp, Dignite.Abp.Notifications.* and Dignite.NotificationCenter.* move to 10.7.0,
    along with @dignite/ng.flex-fields, @dignite/ng.flex-fields-ckeditor and @dignite/ng.notification-center and
    the published Angular library's dependency pins. This lifts the last gate on a stable NuGet release: a stable
    Dignite.Vault.Extract.* no longer depends on a pre-release package (NU5104). No source change, no EF migration.
  • Restore no longer needs GITHUB_PACKAGES_TOKEN. abp-modules 10.7.0 is published to nuget.org only (its
    GitHub Packages feed carries pre-releases), so NuGet.Config drops the github source and its mapping, and the
    duplicate host/NuGet.Config is removed; every package resolves from nuget.org.
  • The stable npm publish step in release.yml treats "already published" as a soft skip, like the pre-release step, so
    a first publish bootstrapped by hand (npm Trusted Publishing cannot create a package) does not fail the release run.
  • NuGet.org publishing moves to NuGet Trusted Publishing (OIDC), like the npm side; no long-lived API key (#711).
Assets 22
Loading