Updating code version because feature is released. Setting date to run script properly.
Details
Details
- Test if yarn script dist/scripts/force-policy-acknowledgment.js works properly.
- Test if accepting policy works on native
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- master
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
keyserver/src/scripts/force-policy-acknowledgment.js | ||
---|---|---|
9 | As I said here it is possible to release this tomorrow: https://phab.comm.dev/D6394#inline-43367. Concrete time is not needed (shouldn't cause any harm) so just pushing the date to the next day |
keyserver/src/utils/validation-utils.js | ||
---|---|---|
166 | We should make this 183 and it should be good to land |
Comment Actions
Requesting review to get the answer
keyserver/src/utils/validation-utils.js | ||
---|---|---|
166 | Sorry, but could you say why is that? All native changes are included in yesterday's release, represented by this commit. I am not sure why we need to bump the version higher |
keyserver/src/utils/validation-utils.js | ||
---|---|---|
166 | Ah okay then we should make it 181 which is the first in the "pair" (181 is the public release paired with 182 which is the staff release) |
Comment Actions
update version to 181
keyserver/src/utils/validation-utils.js | ||
---|---|---|
166 | that makes sense to me, thanks for catching it! |