Bump @cap-js/attachments from 2.0.2 to 3.6.1

[dependabot]

Bumps @cap-js/attachments from 2.0.2 to 3.6.1.

Release notes

Sourced from @​cap-js/attachments's releases.

v3.6.1

Fixed

• Resolved an issue where URLs for nested entities were not generated.
• Fixed an internal server error in CDS 8 caused by the absence of cds.infer?.target.

v3.6.0

Added

• Introduced support for @Validation.MaxItems and @Validation.MinItems annotations, enabling you to define the minimum and maximum number of attachments that can be uploaded.

  Example: Limit to a Maximum of 2 Attachments

  entity Incidents {
      @Validation.MaxItems: 2
      attachments: Composition of many Attachments;
  }

  Example: Require at Least 2 Attachments

  entity Incidents {
      @Validation.MinItems: 2
      attachments: Composition of many Attachments;
  }

• Enhanced the note field to support multi-line input, improving readability for longer text entries.

Fixed

• Prevented unauthorized users from accessing attachments.
• Improved deletion logic for non-draft entities to ensure all associated attachments are reliably removed, preventing orphaned files and maintaining data consistency.
• Handling the use of nested POST requests in non-draft mode.
• Prevent overriding attachments using /content handler.

v3.5.0

Fixed

• Enforced the use of the Content-Length header to prevent server errors.
• Designated the content property in the Attachments table as a NonSortableProperty to prevent database errors when sorting LargeBinary fields.

v3.4.0

Added

• Introduced support for the @Core.AcceptableMediaTypes annotation, allowing specification of permitted MIME types for attachment uploads:

  annotate my.Books.attachments with {
      content @Core.AcceptableMediaTypes: ['image/jpeg'];

... (truncated)

Changelog

Sourced from @​cap-js/attachments's changelog.

Version 3.6.1

Fixed

• Resolved an issue where URLs for nested entities were not generated.
• Fixed an internal server error in CDS 8 caused by the absence of cds.infer?.target.

Version 3.6.0

Added

• Introduced support for @Validation.MaxItems and @Validation.MinItems annotations, enabling you to define the minimum and maximum number of attachments that can be uploaded.

  Example: Limit to a Maximum of 2 Attachments

  entity Incidents {
      @Validation.MaxItems: 2
      attachments: Composition of many Attachments;
  }

  Example: Require at Least 2 Attachments

  entity Incidents {
      @Validation.MinItems: 2
      attachments: Composition of many Attachments;
  }

• Enhanced the note field to support multi-line input, improving readability for longer text entries.

Fixed

• Prevented unauthorized users from accessing attachments.
• Improved deletion logic for non-draft entities to ensure all associated attachments are reliably removed, preventing orphaned files and maintaining data consistency.
• Handling the use of nested POST requests in non-draft mode.
• Prevent overriding attachments using /content handler.

Version 3.5.0

Fixed

• Enforced the use of the Content-Length header to prevent server errors.
• Designated the content property in the Attachments table as a NonSortableProperty to prevent database errors when sorting LargeBinary fields.

Version 3.4.0

Added

... (truncated)

Commits

• afde7d1 Update CHANGELOG for version 3.6.1 and bump version in package.json (#356)
• f9a4658 Internal server error supporting CDS 8 (#355)
• 92b2d0a Nested Entities Missing URLs (#353)
• 0079528 Fix links and formatting in README.md (#352)
• 05cd8ba Prepare release 3.6.0 (#346)
• 8784730 Fixing data preparation of nested POST requests (#336)
• c29ce34 Translation Delivery (#347)
• 24ad403 Fix condition for PR approval check in CI workflow (#345)
• de9ebd2 Enhance attachment deletion handling for non-draft entities (#326)
• ea1fcbd Enhance note field in Attachments aspect to support multi-line text (#342)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​cap-js/attachments since your current version.

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)