Giter Club home page Giter Club logo

Comments (6)

planger avatar planger commented on August 11, 2024 1

I'm not really familiar with the current release process of Blueprint, probably @jfaltermeier should chime in on that!
In general I don't have any objection to tag manually for now. But on the long run, it'd be good to have an automated workflow that creates a Github release and that tags the git ref from which the version has been built.

from theia-blueprint.

jfaltermeier avatar jfaltermeier commented on August 11, 2024 1

Currently each commit on master triggers a build that will be released.
I agree that for now we can add tags manually, but we should look for an automated solution including version increments for each published version.

from theia-blueprint.

marcdumais-work avatar marcdumais-work commented on August 11, 2024

Indeed, we have an initial v0.0.1 tag in the repo, and that's it:
image

Related - ATM we only manually step the version of the Blueprint app, when we update the Theia version. Between these updates, any PR merged, we release new Blueprint packages, that re-uses the same version number.

Probably we should step the version for "in-between" releases, so it's possible to distinguish between them and "official" releases? And also tag "official" releases in the repo (a requirement for at least some companies that want a tag, to fetch the sources of a specific version for analysis)? Also it probably would not hurt to include the version in the package names. i.e. how do we know which version are these?

To recap:

  • step Blueprint version in each app's package.json for each release. e.g. use Theia's version as is done now, but step the minor patch/bugfix version for each merged PR (note: this may sometimes clash with Theia stepping its own patch version, e.g. for community releases or the occasional bugfix release)
  • add a tag in the repo for each "official" release (1.41.0, 1.42.0, ...)
  • include version in package names?

from theia-blueprint.

marcdumais-work avatar marcdumais-work commented on August 11, 2024

cc: @tsmaeder @planger WDYT?

from theia-blueprint.

marcdumais-work avatar marcdumais-work commented on August 11, 2024

As a temporary work-around, are there any objections, to me manually adding a git tag for 1.41.0?

from theia-blueprint.

marcdumais-work avatar marcdumais-work commented on August 11, 2024

release tag manually added: v1.41.0

from theia-blueprint.

Related Issues (20)

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.