chore: updates for release (#35)

* update release.yml

* update package

* update environment

* updates to readme

* update readme

* update readme again

* prettier

* update changelog

* Update README.md

Co-authored-by: Simon Kobler <32038731+KoblerS@users.noreply.github.com>

* Update README.md

Co-authored-by: Simon Kobler <32038731+KoblerS@users.noreply.github.com>

---------

Co-authored-by: Simon Kobler <32038731+KoblerS@users.noreply.github.com>

Author: SirSimon04

.github/workflows/release.yml

@@ -5,16 +5,17 @@ on:
 
 permissions:
   contents: write
+  id-token: write
 
 jobs:
   publish-npm:
     runs-on: ubuntu-latest
-    environment: npm
+    environment: npmjs:@cap-js/print
     steps:
       - uses: actions/checkout@v4
       - uses: actions/setup-node@v4
         with:
-          node-version: 20
+          node-version: 24
           registry-url: https://registry.npmjs.org/
 
       - name: Run Tests
@@ -38,6 +39,4 @@ jobs:
         with:
           tag: "v${{ steps.package-version.outputs.current-version }}"
           body: "${{ steps.parse-changelog.outputs.body }}"
-      - run: npm publish --access public
-        env:
-          NODE_AUTH_TOKEN: ${{secrets.npm_token}}
+      - run: npm publish --access public --provenance

CHANGELOG.md

@@ -4,136 +4,8 @@ All notable changes to this project will be documented in this file.
 This project adheres to [Semantic Versioning](http://semver.org/).
 The format is based on [Keep a Changelog](http://keepachangelog.com/).
 
-## Version 1.0.9 - TBD
+## Version 0.1.0 - TBD
 
 ### Added
 
-- License entry
-
-### Fixed
-
-- Handling of multiple records in one request
-
-### Changed
-
-- prepare for CDS9 in tests
-
-## Version 1.0.8 - 28.03.25
-
-### Added
-
-- Added @UI.MultiLineText to value fields
-- Added support for Multi-Tenancy
-- Added configuration options to disable tracking of CREATE/UPDATE/DELETE operations on a project level
-
-### Fixed
-
-- Handling of numeric and boolean fields was faulty, when an initial value of `0` for numeric or `false` for boolean was supplied
-- Decimal values were handled differently for HANA and SQlite
-- Missing UI Label for one attribute (`ChangeLog.ID`) of the Changes UI facet
-- Support for @UI.HeaderInfo.TypeName as fallback for the UI Label of the key
-- Compilation error when an association is used as a key
-- Fixed handling of unmanaged composition of many
-- Proper casing of the operation enum type
-
-### Changed
-
-- Added warning and mitigation for multi-tenant deployments with MTX
-- Added a disclaimer of upcoming new version having a minimum requirement of CDS 8.6 for multitenancy fix
-- Changed the default limit on non-HANA databases from 255 to 5000 characters for all String values
-- Updated peer dependency from CDS7 to CDS8
-
-## Version 1.0.7 - 20.08.24
-
-### Added
-
-- A global switch to preserve change logs for deleted data
-- For hierarchical entities, a method to determine their structure and a flag to indicate whether it is a root entity was introduced. For child entities, information about the parent is recorded.
-
-### Fixed
-
-- CDS 8 does not support queries for draft-enabled entities on the application service anymore. This was causing: SqliteError: NOT NULL constraint failed: (...).DraftAdministrativeData_DraftUUID
-- CDS 8 deprecated cds.transaction, causing change logs of nested documents to be wrong, replaced with req.event
-- CDS 8 rejects all direct CRUD requests for auto-exposed Compositions in non-draft cases. This was affecting test cases, since the ChangeView falls into this category
-- req.\_params and req.context are not official APIs and stopped working with CDS 8, replaced with official APIs
-- When running test cases in CDS 8, some requests failed with a status code of 404
-- ServiceEntity is not captured in the ChangeLog table in some cases
-- When modeling an inline entity, a non-existent association and parent ID was recorded
-- Fixed handling, when reqData was undefined
-
-### Changed
-
-- Peer dependency to @sap/cds changed to ">=7"
-- Data marked as personal data using data privacy annotations won't get change-tracked anymore to satisfy product standards
-- Restructured Documentation
-
-## Version 1.0.6 - 29.04.24
-
-### Fixed
-
-- Storage of wrong ObjectID in some special scenarios
-- Missing localization of managed fields
-- Views without keys won't get the association and UI facet pushed anymore
-
-### Added
-
-- A method to disable automatic generation of the UI Facet
-
-### Changed
-
-- Improved documentation of the @changelog Annotation
-
-## Version 1.0.5 - 15.01.24
-
-### Fixed
-
-- Error on HANA when logging Boolean or Numeric Data
-
-## Version 1.0.4 - 08.01.24
-
-### Added
-
-- Side effect annotation now allows automatic refresh after a custom action caused changes
-
-### Changed
-
-- Added a check to disable change tracking for views with a UNION
-
-### Fixed
-
-- Handling of associations within change tracked entities
-- Handling of change log when custom actions on child entities are called
-
-## Version 1.0.3 - 10.11.23
-
-### Added
-
-- Added note about using `SAPUI5 v1.120.0` or later for proper lazy loading of the _Change History_ table.
-- In README, add warning about tracking personal data.
-
-### Changed
-
-- Support cases where parent/child entries are created simultaneously.
-- Allow for lazy loading of change history table (with SAP UI5 release 1.120.0).
-
-## Version 1.0.2 - 31.10.23
-
-### Changed
-
-- In README, use view of the full change-tracking table instead of the customized one for the main image.
-
-## Version 1.0.1 - 26.10.23
-
-### Changed
-
-- Flattened README structure.
-
-### Fixed
-
-- Labels are looked up from the service entity (not the db entity only).
-
-## Version 1.0.0 - 18.10.23
-
-### Added
-
-- Initial release
+- Initial release that provides out-of-the-box integration with the SAP Print Service.

README.md

@@ -4,35 +4,29 @@
 
 ## About this project
 
-CDS plugin for SAP Print service (package `@cap-js/print`) is a CDS plugin providing print service features through integration with [SAP Print Service](https://api.sap.com/api/PRINTAPI/overview).
+The `@cap-js/print` package is a [CDS plugin](https://cap.cloud.sap/docs/node.js/cds-plugins#cds-plugin-packages) that provides print service features through integration with the [SAP Print Service](https://api.sap.com/api/PRINTAPI/overview).
 
 ## Table of Contents
 
-- [About this project](#about-this-project)
-- [Requirements](#requirements)
-- [Setup](#setup)
-
 ## Requirements and Setup
 
-See [Getting Started](https://cap.cloud.sap/docs/get-started) on how to jumpstart your development and grow as you go with SAP Cloud Application Programming Model.
-
-Usage of this plugin requires a valid subscription of the [SAP Print Service](https://help.sap.com/docs/SCP_PRINT_SERVICE).
+Using this plugin requires a valid subscription of the [SAP Print Service](https://help.sap.com/docs/SCP_PRINT_SERVICE).
 
 ## Usage
 
-To use this plugin to print documents there are two main steps:
+To use this plugin to print documents, there are two main steps:
 
-1. Make sure your CDS model is modelled correctly
+1. Ensure your model meets the requirements
 2. Annotate your CDS model with `@PDF.Printable`
 
-### Assumptions of your model
+### Model Requirements
 
-- The attribute you want to print is of type `LargeBinary`
-- This attribute has the annotation `@Core.ContentDisposition: fileName`, where `fileName` is the attribute that specifies the file name
+- The attribute(s) you want to print are of type `LargeBinary`
+- Those attributes have the annotation `@Core.ContentDisposition: fileName`, where `fileName` is the attribute that specifies the file name or a hardcoded string with the file name
 
 ### Annotations in CDS model
 
-To use the print plugin, simply annotate your entity with `@PDF.Printable`:
+To use the print plugin, annotate your entity with `@PDF.Printable`:
 
 ```cds
 @PDF.Printable
@@ -42,16 +36,24 @@ entity Books as projection on my.Books;
 This annotation does the following things in the background:
 
 - Adds an action `print` to the annotated entity with the following parameters:
-  - `Queue`: Name of the print queue to use
-  - `Copies`: Number of copies to print
-  - `File`: Only added if the entity has multiple `LargeBinary` attributes. Allows selecting whicn file should be printed. Make sure the `LargeBinary` properties are annotated with `@Common.Label`
+  - `Queue`: Name of the print queue to use.
+  - `Copies`: Number of copies to print.
+  - `File`: Only added if the entity has multiple `LargeBinary` attributes. Allows selecting which file should be printed. Ensure that the `LargeBinary` properties are annotated with `@Common.Label`.
 - This action is added to the UI and a handler is generated to process the print request.
 - An entity `PrintServiceQueues` is added to the service to provide available print queues in a value help.
 - An entity `PrintServiceFiles` is added to the service to provide available files in a value help (only if multiple `LargeBinary` attributes exist).
 
-## Manual usage
+## Manual Usage
+
+You can also use the print service to print documents manually, i.e., without the `@PDF.Printable` annotations and generated actions and handlers.
+
+Use cases for a manual approach could be:
+
+- You want to print documents that are not part of your CDS model, i.e., files generated at runtime.
+- Your model does not meet the requirements for the automatic approach.
+- You want to print a file type other than PDF.
 
-You can also use the print service to print documents manually, i.e. without the `@PDF.Printable` annotations and generated actions and handlers. For this, you can use the `cds.connect.to`-API of CAP to connect to the print service and invoke the `print` action manually.
+For this, you can use the `cds.connect.to` API of CAP to connect to the print service and invoke the `print` action manually.
 
 ```javascript
 const printService = cds.connect.to("PrintService");
@@ -71,19 +73,19 @@ await printService.send("print", {
 const queues = await printService.get("/Queues");
 ```
 
-It is possible that for LargeBinaries, that you get from the database, the content is provided as a stream. In this case, the stream needs to be converted to base64 before passing it to the print service. For an example, have a look at the sample application in `test/bookshop/`
+It is possible that for LargeBinaries retrieved from the database, the content is provided as a stream. In this case, the stream needs to be converted to base64 before passing it to the print service. For example, see the sample application in `test/bookshop/`
 
 ## Local Development
 
-When running the application locally, i.e. `cds watch`, the print service is mocked. This mock implementation prints the print job details to the console instead of sending it to the actual print service. It also provides a number of sample print queues for selection.
+When running the application locally, the print service is mocked. This mock implementation prints the print job details to the console instead of sending them to the actual print service. It also provides a number of sample print queues for selection.
 
 ## Hybrid Testing
 
 You can also run the application locally with a binding to the cloud print service with CAP profiles. For more information, see [Hybrid Testing](https://cap.cloud.sap/docs/advanced/hybrid-testing#hybrid-testing). You need an instance of the SAP Print Service.
 
 ### Local
 
-As the `hybrid` profile of the plugin uses SAP HANA Cloud to execute integration tests in CI, a profile `local` is added that uses can be used to execute the application locally with a binding to the cloud print service.
+As the `hybrid` profile of the plugin uses SAP HANA Cloud to execute integration tests in CI, a profile `local` is added that can be used to execute the application locally with a binding to the cloud print service.
 
 ```bash
 # Once as setup
@@ -100,16 +102,16 @@ For CI, the hybrid integration tests are automatically run against a SAP Print S
 
 ## Support, Feedback, Contributing
 
-This project is open to feature requests/suggestions, bug reports etc. via [GitHub issues](https://github.com/cap-js/print/issues). Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our [Contribution Guidelines](CONTRIBUTING.md).
+This project is open to feature requests/suggestions, bug reports, etc. via [GitHub issues](https://github.com/cap-js/print/issues). Contributions and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our [Contribution Guidelines](CONTRIBUTING.md).
 
 ## Security / Disclosure
 
-If you find any bug that may be a security problem, please follow our instructions at [in our security policy](https://github.com/cap-js/print/security/policy) on how to report it. Please do not create GitHub issues for security-related doubts or problems.
+If you find a bug that may be a security problem, please follow the instructions [in our security policy](https://github.com/cap-js/print/security/policy) on how to report it. Please do not create GitHub issues for security-related doubts or problems.
 
 ## Code of Conduct
 
 We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone. By participating in this project, you agree to abide by its [Code of Conduct](https://github.com/cap-js/.github/blob/main/CODE_OF_CONDUCT.md) at all times.
 
 ## Licensing
 
-Copyright 2025 SAP SE or an SAP affiliate company and print contributors. Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information including third-party components and their licensing/copyright information is available [via the REUSE tool](https://api.reuse.software/info/github.com/cap-js/print).
+Copyright 2025 SAP SE or an SAP affiliate company and print contributors. Please see our [LICENSE](LICENSE) for copyright and license information. Detailed information, including third-party components and their licensing/copyright information, is available [via the REUSE tool](https://api.reuse.software/info/github.com/cap-js/print).

package.json

@@ -2,7 +2,7 @@
   "name": "@cap-js/print",
   "version": "0.1.0",
   "description": "CAP plugin for SAP Cloud Print Service.",
-  "repository": "@cap-js/print",
+  "repository": "cap-js/print",
   "homepage": "https://cap.cloud.sap/",
   "main": "cds-plugin.js",
   "author": "SAP SE (https://www.sap.com)",
@@ -22,7 +22,6 @@
     "plugin"
   ],
   "dependencies": {
-    "@cap-js/print": "file:",
     "@sap-cloud-sdk/connectivity": "^3.26.4",
     "@sap-cloud-sdk/http-client": "^4.1.2",
     "@sap/xssec": "^3.6.2"