Release v0.6.0 - Breaking if used standalone (no GH Action)

This version includes a breaking change if you use the standalone DLL instead of the GitHub Action.
The default settings for PublishStatus and License have been removed.

What's Changed

• remove settings defaults and fix issue where naming conventions were … by @Brend-Smits in #31
• update version to v0.6.0 by @Brend-Smits in #32

Full Changelog: v0.5.0...v0.6.0

Release v0.5.0

What's Changed

• generate slsa-provenance, sbom and clean up sonar file by @Brend-Smits in #25
• Updating Usage section with content and file options by @manasesjesus in #27
• SBOM step in workflow is failing by @Brend-Smits in #29
• fix: sign instead of cosign option by @Brend-Smits in #30
• feat: ignore frontmatter that is not relevant for our settings by @Brend-Smits in #28

New Contributors

• @manasesjesus made their first contribution in #27

Full Changelog: v0.4.2...v0.5.0

Release v0.4.2

What's Changed

• Clean up codebase and apply a major refactor.
• Add new tests (closes #3)
• Add Codescene
• Add SonarQube

Full Changelog: v0.4.1...v0.4.2

Release v0.4.1

• Fix bug that caused problem when trying to post as author. (#17)

  When publishing as an author and not as a publication, it would error because the value of the publication id or name is set as an empty string, and thus is not null.
  Add test to verify author functionality.

Release v0.4.0

This new release adds support for the following:

• Support both Pascal and Underscored Naming Conventions

• Allow posting without publication name or Id

  This feature allows you to post under a specific user, instead of under a specific publication.

  This resolves issue #16

No breaking changes were introduced. Enjoy 🚀

Fix issue where tags are not added

• Fix issue where tags were not added

  Signed-off-by: Brend Smits [email protected]

Add Auto Release

This is mostly a release to test release automation.
Nothing interesting here.

Fix issue resulting in error about missing configuration with some setups

In some cases, when using Frontmatter, the action would error and tell you did not configure the correct settings.
This was an issue with the order of validation checking for the settings. This release fixes this.

Full Changelog: v0.3...v0.3.1

Release v0.3

This release adds the ability to parse frontmatter from Markdown files. The markdown file can include frontmatter as follows:

---
Title: "Title of the post"
Tags: ['interesting', 'tags', 'here']
PublishStatus: "draft"
NotifyFollowers: true
License: "all-rights-reserved"
---

This frontmatter will override previously defined settings. Frontmatter will not be published on Medium. Available types in the frontmatter are Title, Tags, PublishStatus, NotifyFollowers, License, CanonicalUrl, and ContentFormat.

Full Changelog: https://github.com/philips-software/post-to-medium-action/commits/v0.3

Initial release v0.2

Action is still experimental but should be usable.
Please report issues on the issue tracker.

Use the Action like shown below:

jobs:
  execute-action:
    name: Use internal GH Action
    runs-on: ubuntu-latest
    steps:
      - name: Create Medium Post
        uses: philips-software/[email protected]
        with:
           integration_token: "${{ secrets.INTEGRATION_TOKEN }}"
           content: "Content"
           content_format: "markdown"
           notify_followers: "false"
           publication_name: "publication"
           tags: "test,tag"
           title: "Title"