versioning.app

software versioning, made simple

built by @_CalMorris #BuildInPublic

[versioning.app @versioningapp]

we have launched a register interest function on the home page of https://t.co/JKiue2V6ed!

sign up for news on when we launch and future updates!

[versioning.app @versioningapp]

@samm_duc @_CalMorris hey Samuel, indeed it is! super important to get this right from day one - and bake it in at a data fetching level to prevent leaking between workspaces/tenants. for me it was just trying to come up with an elegant solution to manage and maintain permissions really!

[versioning.app @versioningapp]

we have launched a register interest function on the home page of https://t.co/JKiue2V6ed!

sign up for news on when we launch and future updates!

[versioning.app @versioningapp]

update on the #rbac permissions system that i have been building out - how do you define default roles & permissions and maintain them as the app evolves? let's do a deep dive 🧵

[versioning.app @versioningapp]

and this is super neat, because if someone does not log in for months, they will automatically pick up the system roles & permissions, automagically!

[versioning.app @versioningapp]

update on the #rbac permissions system that i have been building out - how do you define default roles & permissions and maintain them as the app evolves? let's do a deep dive 🧵

[versioning.app @versioningapp]

then, when we want to add new permissions or roles, we just increment the permission version, add the permission & reload the workspace... and as if by magic.. it adds the permissions!

[versioning.app @versioningapp]

focused in and building https://t.co/JKiue2V6ed mvp right now

- #rbac and permissions ✅
- #release overview and management ✅
- #deployment overviews ✅
- #cli for external integration ✅
- #launch? soon™️

lets build & ship!

#buildinpublic

[versioning.app @versioningapp]

@ljharb bordeaux, there there are other grape libs out there

[versioning.app @versioningapp]

i now need to get this implemented in all data calls, given our abstractions it shouldn't be a huge challenge, so let's see how quickly it can be implemented...

[versioning.app @versioningapp]

made some small improvements this morning to the permissions engine. we now have the ability to define wildcard permissions, meaning we can grant access to `release*` and get grant access to all sub-resources (or negate). powerful but complex, so docs need to be strong here

[Kent C. Dodds 🏹 @kentcdodds]

New syntax incoming!

https://t.co/sBaJ9USSOp

I think I love it.

[versioning.app @versioningapp]

@Aybee5_ @kentcdodds not looked deep into the implementation here, but suppose your consuming this - you are much more likely to handle the error this way, at least for me when i read the proposed api! you should always be handling errors - so the order in which you destruct shouldn’t matter here?

[versioning.app @versioningapp]

@dgut_ hey David! we’re building a platform to unify and simply the release of software with deep integrations! changelog auto generation, deployment status with rollback & gated approvals for different environments (think qa approval before deployment to production - that kinda thing!)