logto VS changesets

feature request: add suspend user event for webhook #4297

We'd like also invite you to take a look at our new website and explore the features of Logto Cloud.

Want to give it a try? Go to Logto Cloud and pick a connector.

Thanks for the great feedback :)! We're pleased to confirm that we do offer support for our Hobby plan. However, if you're looking for premium support with a response time of 48 hours, that's part of our Pro Plan. Additionally, Logto has a vibrant community that is always ready to assist with any issues you may encounter. When it comes to pricing, ours is based on Monthly Active Users (MAU) and user engagement. For an app with around 10k MAUs, you can expect an approximate cost of $100 per month, based on our prediction and industry benchmarks. We make a point of being transparent about our pricing on our website, so our customers can make informed decisions with confidence. In terms of cost, we believe our prices are competitive within the industry. As a SaaS company, we specialize in providing comprehensive identity management services. Our solutions adhere to open standards and cover essential aspects like user sign-in/sign-up and user management features such as role-based access control. If our Freemium or Hobby plans don't meet your needs, we also offer a fully open-source version. This option is highly regarded within the open-source community and might be a suitable choice for you. https://github.com/logto-io/logto

Security is a complex topic, and it is impossible to cover everything in a single article. We hope that this article has helped you build a stronger sense of security for yourself or your team. If you are building a new app, you may also want to check out Logto, a platform that helps you develop, manage, and secure your product's user identities with minimal effort.

Learn more details in the blog: 👉 Tackle social login experience: Unlocking the power of convenience. From the perspective of Increase Conversion, Get Quality Data, and Retain Users, I explored the benefits of Social Login and offer some tips with comparative case studies. Additionally, you can experience the seamless sign-in experience configuration firsthand within Logto Cloud Console. Value your insights if you have any better suggestions.

Logto is an effortless identity solution with all the features you need. It supports various sign-in methods, including username, email, phone number, and popular social sign-ins like Google and GitHub.

In my circles, this is the go-to for release automation / changelogs: https://github.com/changesets/changesets

🦋 Publicando com changesets

Open source libraries and frameworks share a common necessity: the need to develop multiple packages cohesively and efficiently while managing their versioning and publishing to NPM. Nx has emerged as a go-to choice for handling such open source monorepos (as we'll explore further in the next section of this blog post). Until recently, one area Nx did not address directly was versioning and release management. Traditionally, this gap has been filled with tools like release-it, changesets, or custom Node scripts, similar to our approach in the Nx repository.

Doing these tasks by hand can quickly become a hassle. If you're open to receiving contributions from others, it can be an even bigger headache. In this post we'll cover how to use changesets to automate all of these steps.

For versioning we use changeset, but with fixed-packages. We have found that the user thinks updating and managing our dependencies much easier if they can just bump each package to the same version. (storybook, sanity follows this appoach). While it feels unintuitive that each package gets a major if just the CSS has breaking changes, the user don't really care. They just want to finish the chore of updating their dependencies fast, without having to understand the system that deeply. This also makes documenting the changes much easier!

Thanks for sharing this. Why should I choose that instead of Changesets that work like a charm?

You’re right this information would be better suited for for commit trailers. A lot more information can be put there as well. For the purpose of changelog generation, what it’s commonly used for, it could just as well be put in the trailers and not crammed into the subject. I personally prefer changesets though.