CVSmia

Product updates

Changelog

Improvements and fixes in CVSmia.

0.0.0-beta.319

  • CVSmia is now available in Ukrainian. Select `Українська` under Settings > General > Language.
  • The installer is also available in Ukrainian, with license terms in the same language.

0.0.0-beta.318

  • Import and export keep the application window responsive during processing.
  • Different resume entries with the same employer name can be selected separately.
  • Concurrent changes and deletions are handled more clearly when saving in multi-user mode.
  • AI selection respects the selected confidence threshold even when all suggestions fall below it.
  • Resume previews protect single-use data even during concurrent requests.

0.0.0-beta.313

  • CVSmia is now available in German. Select `Deutsch` under Settings > General > Language.
  • The installer is also available in German, with German license terms.
  • CVSmia is now available in Swedish and Danish. Select `Svenska` or `Dansk` under Settings > General > Language.
  • The installer is also available in Swedish and Danish, with license terms in the same language.

0.0.0-beta.309

  • No new end-user features.
  • Startup verification of paid licenses is now stricter.
  • Temporary network failures are still handled without locking out the user when the local license policy permits continued use.
  • Invalid or manipulated license data from local storage is no longer used as an access grant.
  • Invalid responses from the license server can no longer override a valid local license.
  • Locally stored license data is protected per Windows user.
  • Signature, issuer, audience, license binding, and validity periods are checked more strictly before server-controlled modules are used.

0.0.0-beta.269

  • No new end-user features are included in this release.
  • The update and publishing flow is now more robust, making it easier to publish and follow up new versions on the product website as well.
  • The release flow now avoids an authentication conflict between GitHub Actions and the website repository, so website updates via PR can complete as intended.
  • No noticeable security or privacy changes for end users in this release.

0.0.0-beta.268

  • No new end-user features are included in this release.
  • The update and publishing flow is now more robust, making it easier to publish and follow up new versions on the product website as well.
  • The release flow now avoids an authentication conflict between GitHub Actions and the website repository, so website updates via PR can complete as intended.
  • No noticeable security or privacy changes for end users in this release.

0.0.0-beta.267

  • No new end-user features are included in this release.
  • The update and publishing flow is now more robust, making it easier to publish and follow up new versions on the product website as well.
  • The release flow now avoids an authentication conflict between GitHub Actions and the website repository, so website updates via PR can complete as intended.
  • No noticeable security or privacy changes for end users in this release.

0.0.0-beta.265

  • No new end-user features are included in this release.
  • The update and publishing flow is now more robust, making it easier to publish and follow up new versions on the product website as well.
  • The release flow now avoids an authentication conflict between GitHub Actions and the website repository, so website updates via PR can complete as intended.
  • No noticeable security or privacy changes for end users in this release.

0.0.0-beta.259

  • No new end-user features are included in this release.
  • The update and publishing flow is now more robust, making it easier to publish and follow up new versions on the product website as well.
  • The release flow now avoids an authentication conflict between GitHub Actions and the website repository, so website updates via PR can complete as intended.
  • No noticeable security or privacy changes for end users in this release.

0.0.0-beta.229

  • No new end-user features are included in this release.
  • This release contains technical improvements and behind-the-scenes stabilization.
  • The update and publishing flow has been made more robust to support safer delivery of new versions.
  • No noticeable security or privacy changes for end users in this release.