Coder Social home page Coder Social logo

release-me's People

Contributors

dependabot[bot] avatar kevin-de-jong avatar

Stargazers

 avatar  avatar  avatar  avatar

release-me's Issues

Read Changelog-configuration from repository

Context

The generated changelog in the GitHub Release is build to allow for flexible configuration (similar to GitHubs generating release notes).

However, the configuration is currently static and not read from .github/releases.y[a]ml.

Proposal

  • Retrieve the contents of the configuration file (.github/releases.y[a]ml) using the REST API
  • Apply configuration during release notes generation.

problems with release assets

I'm having a couple of issues:

  • I have a local .zip file I want to attach as a release asset. For some reason when release-me uploads it, it doubles in size and becomes unopenable. It's getting corrupted somehow. This happens if it's added as an artifact or a local file.

  • This doesn't seem to be compatible with version 4 of upload-artifact ( 'actions/upload-artifact@v4' ). If you try to use this task, the artifact isn't found by release-me. Perhaps support could be added?

Support SemVers "Initial Version"

Context

SemVer defines a project to remain in "Initial Version" during initial development. During this phase, the API is unstable and therefore breaking changes are not resulting in updating the MAJOR version.

Proposal

Implement support for Initial Version

Add support for CalVer versioning

Context

Currently automatic versioning is based on Conventional Commits and SemVer 2.0.
However, we would like to offer CalVer as an additional strategy.

Proposal

  • Introduce a configuration option to select version strategy
  • Allow extended configuration of CalVer (formatting (e.g. YYYY.MM.MICRO) and mapping between conventional commit types and increments (e.g. breaking changes & feat > CALENDAR, fix > MICRO, others > MODIFIER))

Fail to find conventional commit ended by pull request number with round brackets

Context

When merging a github pull request, the default commit message contains the pull request number with round brackets in the end. And it can't be found during retrieving conventional commits.
Here is an example:

feat(login): add support google oauth (#12)

Proposal

Fix conventional commit matching implementation to support commit with round brackets in description.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.