[andresvillenas]

Summary

Prepares the 1.1.0 release. It's documentation and version references only; no library or client code changes.

• Directory.Build.props: VersionPrefix 1.0.0 → 1.1.0. This only affects local dotnet pack builds; the release workflow takes the version from the tag.
• README.md: version matrix and install command → 1.1.0.
• docs/Usage-Guide.md: install command → 1.1.0, and the Clone form steps now mention the 200-character name limit ([Bug]: Client type check fails and is not run in CI #26).
• docs/Release-Process.md:
  • Replaces the out-of-date "The next planned release is 1.0.0" line. The new text says that adding public API, even to support a fix, is a minor release, with 1.1.0 as the example.
  • The tag example is now v1.1.0.
• Client/package.json + lockfile: private package version 1.0.0-beta.4 → 1.1.0. The lockfile change is limited to the two root version fields, and the built admin bundle is unchanged (same entry.kxh.7e28d654… hash).

Why 1.1.0 rather than 1.0.1: since v1.0.0, the public API gained five optional UpperSubmissionId properties (#27, for #24). Nothing was removed or changed, so it's backward compatible. SemVer still requires a minor release for new public API.

After merge

Following docs/Release-Process.md:

1. Tag v1.1.0 on main and push the tag.
2. Approve the nuget-release deployment.
3. Verify the package on NuGet.org.
4. Create the GitHub release with the notes below.

Draft release notes: Forms Toolkit 1.1.0

Bug fixes for submission export, submission removal, and form cloning, plus compatibility verified through Xperience by Kentico 31.9.0. Fully backward compatible. This is a minor release because one fix added optional public API members.

Fixed

• Export these first in Advanced delete now exports exactly the submissions the preview counted, including the Number of records limit. Previously it exported every submission in the date range (#22).
• Advanced delete no longer deletes or exports submissions created after the preview. Previously, a submission received between Preview matching count and Delete could be deleted without having been previewed or backed up. This was most likely with an empty or current To date. The preview now fixes the set of submissions, and Export these first and Delete act on exactly that set (#24).
• Clone form enforces the 200-character name limit in the dialog, with an inline message. Previously the field accepted any length and the name was rejected only after selecting Clone (#26).
• Advanced export and Advanced delete accept a To date of 12/31/9999 and treat it as no upper bound. Previously it failed with a generic error (#31).

API additions

• New optional UpperSubmissionId init properties on FormSubmissionRemovalRangeRequest, FormSubmissionRemovalOptions, FormSubmissionRemovalPreviewResponse, FormSubmissionExportCommandRequest, and FormSubmissionExportOptions. Existing constructors and service interfaces are unchanged. When the property is omitted, behavior is the same as in 1.0.0.

Maintenance

These changes don't affect the published package:

• Component tests for the administration client, and client type checking in CI (#25, #26).
• Updated vulnerable build-tooling dependencies (#30).

Compatibility

• Xperience by Kentico 30.11.0 or newer; verified through 31.9.0. The packed NuGet package was built and runtime smoke-tested at both 30.11.0 and 31.9.0, covering the admin UI, all three export formats, both delete paths, and form cloning. See Compatibility.md.
• .NET 8.0

Install

dotnet add package XperienceCommunity.FormsToolkit --version 1.1.0