Publish new release

[github-actions]

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

@lowdefy/modules-mongodb-plugins@0.11.0

Minor Changes

• #100 dd309b8 Thanks @JohannMoller! - Log file downloads for parity with upload/delete auditing. The FileManager
  block now fires an onDownload event (payload { fileDoc }) when a download is
  initiated. The file-manager / file-card components expose a new on_download
  var (action list, default []) for consumer-supplied handlers, and — when
  log_events is on — record a download-file event via the events module,
  matching how uploads and deletes are logged.

@lowdefy/modules-mongodb-files@0.11.0

Minor Changes

• #100 dd309b8 Thanks @JohannMoller! - Log file downloads for parity with upload/delete auditing. The FileManager
  block now fires an onDownload event (payload { fileDoc }) when a download is
  initiated. The file-manager / file-card components expose a new on_download
  var (action list, default []) for consumer-supplied handlers, and — when
  log_events is on — record a download-file event via the events module,
  matching how uploads and deletes are logged.

• #100 dd309b8 Thanks @JohannMoller! - Export the files module's download-policy request as a named component so it can
  be consumed outside the file-manager / file-list components. Consumers that
  render downloadable files themselves — such as the events module's
  EventsTimeline — can now _ref it inside a page's requests: list:

  requests:
    - _ref:
        { module: files, component: download-policy, vars: { block_id: <id> } }

  This yields a presigned-GET request with id download_policy_<block_id> on the
  module's files-bucket connection, which the consumer passes as its
  s3GetPolicyRequestId. Previously the only module-owned download policy lived
  inside file-manager / file-list, forcing consuming apps to keep their own
  copies.

• #100 dd309b8 Thanks @JohannMoller! - Expose the FileManager upload-modal form slot on the file-manager and
  file-card components. Consumers can now pass a form_fields block list
  (with field ids <block_id>.form.*) that renders in a post-upload modal;
  the entered values are persisted to the file document's metadata. Adds an
  ok_text var (modal confirm-button label) alongside the existing
  modal_title. When the injected form includes a <block_id>.form.file_category
  field, its value sets the saved document's top-level file_category; the
  build-time file_category var is used as the fallback, so existing consumers
  that pass no form are unaffected.

@lowdefy/modules-mongodb-activities@0.11.0

@lowdefy/modules-mongodb-companies@0.11.0

@lowdefy/modules-mongodb-contacts@0.11.0

@lowdefy/modules-mongodb-events@0.11.0

@lowdefy/modules-mongodb-layout@0.11.0

@lowdefy/modules-mongodb-notifications@0.11.0

@lowdefy/modules-mongodb-release-notes@0.11.0

@lowdefy/modules-mongodb-user-account@0.11.0

@lowdefy/modules-mongodb-user-admin@0.11.0

@lowdefy/modules-mongodb-workflows@0.11.0