feat: update output delimiter & include notes if present

[carloscortonc]

Hi @felipecrs , first of all thank you for this plugin. I was looking for a way to preview the release on open PRs, and your plugin helped me with that.

One thing it was missing was nextRelease.notes, to easily preview and verify release notes. For that, I applied a patch to your npm module: https://github.com/carloscortonc/rpi-cli/blob/7adf997dade8ed5fe119a15165625002dec2c66b/patches/semantic-release-export-data%2B1.1.1.patch

Just exporting nextRelease.notes generated an error, because the content is multi-line (https://github.com/carloscortonc/rpi-cli/actions/runs/18257911158/job/51981820460#step:6:289)
I reviewed how @actions/core::setOutput solved it, and is by using a custom delimiter.

Proposed changes

The proposed changes are:

• Include nextRelease.notes in a new output variable new-release-notes
• Define custom delimiter so output-setting works with multi-line values

These changes in action can be seen here by using this workflow

[felipecrs]

@carloscortonc thanks for the contribution.

I made some changes in 2f3cc34.

Mind taking a look?

[felipecrs]

Release notes can be quite big. Logging it would be problematic. Besides, semantic-release already logs the release notes.

Also, release notes are always set as per semantic-release's type:

https://github.com/semantic-release/semantic-release/blob/422fb20fd45e8fd7f16273de5e68ad61168750e7/index.d.ts#L381

[carloscortonc]

Looks fine @felipecrs 💯

[felipecrs]

Thanks a lot!

[github-actions]

🎉 This PR is included in version 1.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀