781a300bf7
4.0.0-alpha.2
2021-04-13 13:56:26 +02:00
0eb132c025
feat: unleash v4 will require node 14 or higher ( #784 )
2021-04-13 09:22:37 +02:00
223bbbb50d
fix: upgrade unleash-frontend to latest alpha
2021-04-12 20:29:00 +02:00
9bd425c193
feat: Add username/password authentication ( #777 )
2021-04-09 13:46:53 +02:00
99fd210392
feat: added basic email-service ( #780 )
...
* feat: added basic email-service
* feat: preview endpoint for plaintext/html templates
* chore: Updated docs
fixes : #757
2021-04-09 11:16:06 +02:00
696004b5ec
4.0.0-alpha.1
2021-03-30 15:59:14 +02:00
e0682fd8fb
chore: upgrade frontend 4.0.0-alpha.1
2021-03-30 15:58:36 +02:00
baf750c05a
feat: upgrade unleash-frontend to 4.0.0-alpha.0
2021-03-30 15:21:02 +02:00
58137b8579
4.0.0-alpha.0
2021-03-29 20:33:01 +02:00
dfb890c638
Feat: Api-Tokens ( #774 )
...
fixes : #774
2021-03-29 19:58:11 +02:00
f2de0aba65
3.17.4
2021-03-26 14:45:27 +01:00
7a29e344c9
fix: upgrade unleash-frontend to version 3.14.1
2021-03-26 12:38:29 +01:00
205ad921d4
Tags and tag types to ts ( #772 )
...
* chore: Converted tag-store and tag-type-store to ts
* chore: Converted tag service and tag type service to ts
2021-03-26 11:03:30 +01:00
2e13bb9368
Make sure we keep the announced status of each app ( #770 )
...
* Make sure we keep the announced status of each app
- Since we were running onConflict().merge() we were keeping our entire
new object from our remapRow method, and that was overwriting the
current announcement status of the row back to false, unless we'd by
random chance actually set the announced property on our row to be
inserted.
* Add migration for cleaning up application-created events
-
fixes : #769
2021-03-23 12:43:33 +01:00
839ae7fc78
3.17.2
2021-03-19 12:04:54 +01:00
864e01e491
3.17.1
2021-03-18 09:56:49 +01:00
04bfa748f9
3.17.0
2021-03-12 13:06:17 +01:00
9ebb398fa6
feat: upgrade unleash-frontend to version 3.14.0
2021-03-12 11:50:12 +01:00
e1fbe9d013
feat: Default roles and RBAC permission checker. ( #735 )
...
This PR Introduces first steps towards RBAC according to our specifications. Rbac will assume users to exist in the Unleash user table with a unique id. This is required to make correct mappings between users and roles.
2021-03-11 22:51:58 +01:00
efe6507263
chore/update-fe ( #753 )
2021-03-08 15:44:51 +01:00
b24f68d4f8
3.16.0
2021-03-05 16:03:45 +01:00
020b9beb13
chore: update frontend version ( #749 )
2021-03-05 11:47:33 +01:00
4808eb32ff
feat: add support for bulk operations on client apps/instance registr… ( #744 )
...
* feat: add support for bulk operations on client apps/instance registration
-- stores client registrations for 5 seconds, then runs distinct and inserts them into db
fixes : #732
2021-03-04 12:54:13 +01:00
69da866595
3.15.0
2021-02-26 13:59:15 +01:00
f9fd65a4bf
chore: update dependencies ( #737 )
2021-02-26 10:53:45 +01:00
7f34785af1
fix: update unleash-frontend dependency ( #736 )
2021-02-25 16:00:37 +01:00
7cc2334621
fix: upgrade unleash-frontend to version 3.13.1
2021-02-24 12:29:43 +01:00
2e13976b54
3.14.0
2021-02-24 12:29:43 +01:00
1ed3806bb3
feat: upgrade unleash-frontend to version 3.13.0
2021-02-24 12:29:43 +01:00
44af41547e
feat: make client features endpoint memoizable ( #734 )
2021-02-24 12:29:39 +01:00
8cd19254c5
Move deps to devDependencies and add airbnb eslint rules
2021-02-22 22:05:51 -07:00
d1933bcd1b
chore: Add TS support to code coverage
2021-02-22 21:58:29 -07:00
94b278a887
Add support for TS to eslint
...
See https://khalilstemmler.com/blogs/typescript/eslint-for-typescript/
2021-02-22 21:57:58 -07:00
73239d4062
3.13.0
2021-02-19 12:52:53 +01:00
1ba029de66
feat: update unleash-frontend to version 3.12.0
2021-02-19 12:36:21 +01:00
ba57822d23
fix: generate uuid in js migration instead of from db
2021-02-19 11:27:29 +01:00
4902161b39
fix: TypeScript should be a dev dependency ( #730 )
2021-02-19 08:18:48 +01:00
d017ec7cdc
feat: add db-session store ( #722 )
...
* Moves to db managed sessions.
2021-02-18 09:03:21 +01:00
4e63512ee1
Setup tsc-watch for dev build ( #723 )
2021-02-15 08:39:28 +01:00
8d1851cff3
3.12.0
2021-02-12 12:50:34 +01:00
c1aab06798
Feature/setup typescript
...
This sets up the typescript compiler.
Allowing gradual migration to typescript.
Co-authored-by: Christopher Kolstad <chriswk@getunleash.ai >
Co-authored-by: Ivar Conradi Østhus <ivarconr@gmail.com >
Co-authored-by: Fredrik Oseberg <fredrik.oseberg@getunleash.ai >
Co-authored-by: Clint Checkett <clintchecketts@churchofjesuschrist.org >
fixes : #676
2021-02-12 11:42:00 +01:00
feb83772ec
chore: Remove git add from husky
2021-02-11 14:08:33 +01:00
dcde06b0c3
3.11.2
2021-02-09 22:48:04 +01:00
073b679e7e
fix: update unleash-frontend to version 3.11.4
2021-02-09 22:01:00 +01:00
3032ed9f58
fix: include frontend bug fix
2021-02-09 13:50:44 +01:00
566ee16629
fix: upgrade unleash-frontend to version 3.11.3
2021-02-09 12:52:02 +01:00
aff5f2f8b6
3.11.0
2021-02-09 11:07:46 +01:00
8c6bc9f118
Merge pull request #712 from Unleash/fix-711-conflict-on-existing-tag
...
Make feature-toggle-store return 409
2021-02-09 10:54:05 +01:00
cf1092881c
fix: upgrade unleash-frontend to version 3.11.2
2021-02-09 10:45:12 +01:00
063d3f0e4a
Make feature-toggle-store return 409
...
- After seeing frontend behaviour where the user could add the same
tag multiple times, and not get errors or be stopped doing so, we'll
change the backend to return a 409 if you tag a feature with a tag it
already has.
- Previous to this commit, the setup was to do `onConflict().ignore()`
which caused the frontend to not get any help from the backend as to
whether or not the operation was allowed
- This fix adds a custom error and adds a branch to the handleError util
method for handling just that error type with a 409.
- This caused a couple of tests to receive 409, probably due to
insufficient cleanup between tests. Adding faker as a dev-dependency and randomising
toggle names and tag values for each test reduces the chance that
we'll run into duplicate issues in the future for the tests that
touches this problem
fixes : #711
2021-02-08 16:22:15 +01:00
Ivar Conradi Østhus