Giter Club home page Giter Club logo

Comments (3)

brettdh avatar brettdh commented on August 17, 2024

I'm getting close to the first release for my expo bare project and I'd like to start using standard-version before I do - so I'd love to contribute to addressing this gap.

My main question before I get started is whether bumpers for the xcode and gradle files are all that's needed here. I kind of want to zoom out a bit first and ask if you happen to know of (or have written! 🙂 ) a good resource regarding how semver even applies to Expo projects. I have a few initial thoughts, having no experience actually trying this out yet but just from intuition:

  • Breaking changes mean a new app store version and a new Expo release channel.
  • Non-breaking changes are just a new expo publish within the latest Expo release channel.
  • However, this seems to imply that only the major version matters for the app store releases, since minor and patch updates would be done as publishes within that major release's Expo release channel.

Since Expo apps have this inherent divide between one part (the shell app) that's released more like an npm package and another part (the JS bundle) that's released more continuously (within a release channel), I'm wondering where standard-version sits in a typical Expo-based release pipeline, with the considerations above in mind. I think hearing your perspective on this might help me approach the problem more thoughtfully. I read your blog on the topic of standard-version-expo, but I didn't notice anything about release channels.

Interestingly, this all applies just as well to managed-workflow projects; it's just that the possible variety of breaking changes there is much smaller than in bare-workflow projects. This makes me even more certain that you or someone must have thought of this already - so I'd love to hear what you think.

Thanks!

from standard-version-expo.

brettdh avatar brettdh commented on August 17, 2024

@byCedric Since I made the above discussion a lot bigger than just this one issue, I've moved it here: https://forums.expo.io/t/how-to-handle-releases-and-changelogs-with-conventional-commits/42611

I'm about ready to start working on the native version bumpers described here; I'll ping you when I have a PR.

from standard-version-expo.

summerkiflain avatar summerkiflain commented on August 17, 2024

can we get #17 merged, need it urgently...

from standard-version-expo.

Related Issues (15)

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.