Releases: meili-NG/meiliNG.js
Ver. 0.8.1
This version fixes authentication endpoint was reverted to pre-0.7.0 state.
Ver. 0.8.0
Welcome back!
We're now releasing Meiling Gatekeeper version 0.8.0! 🥳
This version introduces several breaking changes.
What's new?
- misuse of term on API errors were fixed.
/v1/meiling/authorization
is now obsolete and won't be supported.- Moved
Meiling.V1.Authorization
toMeiling.V1.Authentication
.
Thank you for choosing Meiling Gatekeeper.
See you on next release!
Ver. 0.7.1
Welcome back!
We're now releasing Meiling Gatekeeper version 0.7.1! 🥳
What's new?
Fixed bugs, Lots of bugs!
The following bugs are patched on this release:
isPrimary
updates onphone
andemail
via/v1/admin
endpoints did not work properly.
Fixed by @Baw-Appie- Now supports
birthdate
onid_token
! 🥳 - fixed the bug that authorized apps are not shown properly on user endpoints
Thank you for choosing Meiling Gatekeeper.
See you on next release!
Ver. 0.7.0
Welcome back!
We're now releasing Meiling Gatekeeper version 0.7.0! 🥳
First of all, 0.7.0 has lots of changes. consequently bringing a lot of breaking changes.
What's new?
Meiling now utilizes filterJson
of prisma
Meiling now utilizes filterJson
, which allows users to filter JSON in prisma queries.
this substatially increases performance (but optimizations should be made in the code).
especially in admin endpoints.
But due to this change, Only MySQL and MariaDB will be supported from this version. Sorry!
Custom signup flows? checked.
If you are using custom signup flows, You can now generate users via /v1/admin/users
endpoint.
and disabling it is easy, just set MEILING_SIGNUP_ENABLED
to false
.
JSON Filtering? checked.
With new admin API allows direct query to Prisma, you can allow other applications in your infrastructure to easily find a user you need.
Confusing words? fixed.
This version of Meiling fixes misuse of terms, especially, Authorization
and Authentication
.
This word is now fixed (including database) in 0.7.0 (more specifically, #27).
Due to changes in database, Your database should be migrated manually.
Please follow the directions on: Migrating database from 0.6.x to 0.7.0
Yes, We are working on SAML 2.0
This version adds "stub"
SAML 2.0. Stay tuned for more SAML 2.0 support news for later on!
Locking properties of Users? Done.
By utilizing new property, lockedProps
, You can prevent users from updating their profile.
ADMIN_TOKENS
? not a requirement any more.
Meiling Gatekeeper previously required ADMIN_TOKENS
fields for startup.
This is no longer a requirement.
Metadata on App? Added.
You can now include additional data on OAuth2 Application.
TL;DR
- Includes a lot of breaking changes,
Refer to: Migrating database from 0.6.x to 0.7.0 for proper migration method. - Signup flows can be disabled
- OAuth2 app now has metadata field
- Prevent user from updating profile via
lockedProps
- Fixed terms
- JSON Filtering support and rawQuery support on prisma
Thank you for choosing Meiling Gatekeeper.
See you on next release!
Ver. 0.6.2
Welcome back!
We're now releasing Meiling Gatekeeper version 0.6.2! 🥳
What's new?
Added License Extension
Thank you for choosing Meiling Gatekeeper.
See you on next release!
Ver. 0.6.1
Welcome back!
We're now releasing Meiling Gatekeeper version 0.6.1! 🥳
What's new?
Removed prisma/migrations
Since prisma db push
is now out of preview feature, It is now a recommended way to deploy your database for meiling.
TL;DR
* No more upstream provided migrations! You tweak meiling gatekeeper to fit your way!Thank you for choosing Meiling Gatekeeper.
See you on next release!
Ver. 0.6.0
Welcome back!
We're now releasing Meiling Gatekeeper version 0.6.0! 🥳
This release was released since a breaking change was made in /common
What's new?
Cleanup on OAuth2
interface names
No more OAuth2QueryParamsForAccessToken
gibberish!
Thank you for choosing Meiling Gatekeeper.
See you on next release!
Ver. 0.5.0
Welcome back!
We're now releasing Meiling Gatekeeper version 0.5.0! 🥳
What's new?
Full refactoring on common
directory, EVEN MORE!
Some common
functions are located on /routes
not /common
where it should be located.
This update will enhance your code-readability for the future meiling development. (not for now, It is still in WIP)
If you have any code that modifies common
or any meiling behavior, Please migrate to Meiling
namespace instead.
Enforced Pagination on /v1/admin/users
Due to massive query that causes timeout on "Prisma Engine", /v1/admin/users
will have pagination by default.
Added /v1/admin/users/count
This update adds /v1/admin/users/count endpoint. This will enable you to get Usercount without querying /v1/admin/users
entirely.
TL;DR
- This update includes entire refactoring of
/common
. - new
/v1/admin/users/count
endpoint! /v1/admin/users
now have pagination enabled by default.
Thank you for choosing Meiling Gatekeeper.
See you on next release!
Ver. 0.4.14
Welcome back!
We're now releasing Meiling Gatekeeper version 0.4.14! 🥳
What's new?
Full refactoring on common
directory
Do you remember the .ts
file mess on common
directory? I do.
On 0.4.14, Those .ts
mess are structured via directory structure. plus, you can now call common functions via namespaces! (e.g. Meiling
, Terminal
, OAuth2
)
This update will enhance your code-readability for the future meiling development. (not for now, It is still in WIP)
"Main Guard" on ./src/index.ts
.
If you are creating script that refers variable on ./src/index.ts, this will be helpful for you.
This version contains several breaking change if you heavily modified meiling gatekeeper on its internals.
If then please update your code to use Meiling
namespace instead.
TL;DR
- This update enhances stability of Meiling Gatekeeper on Node 16.x.
- This software got full face-lift on
common
directory. If you have any modification on it, Please use newly createdMeiling
namespace!
Thank you for choosing Meiling Gatekeeper.
See you on next release!
Ver. 0.4.13
Welcome to release version 0.4.13, which is still, a preview release but includes some patches for node 16.x
What's new?
Proper node 16.x support
Now with Prisma 3.7.0, Prisma ORM now WORKS on Node 16.x platforms.
changes on REFRESH_TOKEN
expiration
The default 7-day term of the previous refresh_token was too short for offline apps, Therefore I extended the lifespan of refresh token to 30 days by default.
This is a breaking change if you are using default configuration. If then please update your .env
file.
Thank you for choosing Meiling Gatekeeper.
See you on next release!