standard-version VS expo

Dive deeper into the world of Husky with the official documentation. Explore the capabilities of Standard Version through its comprehensive documentation. Unravel the mysteries of semantic-release with its detailed documentation. Discover the versatility of bumpp with its comprehensive documentation.

We can use standard-version tool to generate a changelog, bump the version of app and create a new tag automatically.

There are many great tools to help with automation here, some of them are action-semantic-pull-request to enforce conventional commits and standard version to bump the version and create a changelog according to the conventional commits.

I tried gitmoji and followed Make everyone in your project write beautiful commit messages using commitlint and commitizen by @sohandutta, but end up using the setting in this article because it's not compatible to changelog generation of standard-version (Ref: Issue #859)

As a bonus point, the issues you create in your repository can also serve as part of the documentation. You can outline new features there and you will even be able to generate changelogs from the merged pull requests (like I do using conventional-changelog/standard-version).

There’s also a husky precommit hook with ESlint and Prettier fixing and formatting changed code on every commit with lint-staged which makes sure malformed code doesn't even make it to the Pull Request. Combined with standard-version and strict commit messages it makes releasing and changelog generation a breeze. For a contributor the workflow is as smooth as:

But you can also automate even more, if, for example, you write according to Conventional Commits, you can also automate the creation of tags using the standard-version library.

# Changelog All notable changes to this project will be documented in this file. See \[standard-version\](https://github.com/conventional-changelog/standard-version) for commit guidelines. ## 1.1.0 (2021-07-12) ### Features * **new-feature:** add a new-feature to our project 11c0322

Standard Version

So this is like standard-version with less features?

I am using expo setup with tabs template.

Before we begin working on our project, we must set it up and install all the necessary dependencies. We will be using Expo for this project. Expo is a React Native management tool that handles a lot of heavy stuff for us, such as efficiently compiling code and assets, as well as provides us with a productive development environment. Also we will be using Typescript for this project, but don't worry, the process is practically identical to Javascript, so if you don't know Typescript that's fine. This article assumes some basic understanding of React and React Native , such as components, hooks and state. You must also have Node.js installed on your computer.

Expo saves us from the complex configurations required to create a native application with the React Native CLI, making it the easiest and fastest way to build and publish React Native apps.

- Try to unblock usage of Google Maps in my ReactNative Android, iOS and Web App. Context: "https://github.com/expo/expo/issues/23347#issuecomment-16264...

- Provide financial report to investors (this will likely take at least two blocks)

- Fix initial Zoom setting for Google Maps in my app for web. Context: https://github.com/teovillanueva/react-native-web-maps/issue...

- Check on analytics + user enqueries and write (back) to at least 3 of our most active users in the last couple of days

Timeblock exhausted. Posting this and jumping on first task from above.

But some bugs don't get fixed for years. E.g. there was an issue with expo-secure-store not working well on android after app reinstallatiins. It apparently got fixed now 5 years after it was reported: expo-secure-store bug