summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/rangehttpserver
diff options
context:
space:
mode:
authorMaximilian Bosch <maximilian@mbosch.me>2022-10-27 23:31:54 +0200
committerMaximilian Bosch <maximilian@mbosch.me>2022-10-27 23:36:23 +0200
commit6e49dfc7549d3d93f5538cfe776df647bbb01b3f (patch)
tree0a331d127dc6fc569d518784316560ed2b4e4a67 /pkgs/development/python-modules/rangehttpserver
parent79b1ed61d389cadae616e8811e0f8a6bcd0dee7c (diff)
element-{web,desktop}: 1.11.10 -> 1.11.12
ChangeLogs: * https://github.com/vector-im/element-web/releases/tag/v1.11.11 * https://github.com/vector-im/element-web/releases/tag/v1.11.12 Also, it has apparently been forgotten to regenerate `yarn.lock` on the release, `element-web` failed to build like this initially: yarn install v1.22.19 [1/4] Resolving packages... error Couldn't find any versions for "browser-request" that matches "^0.3.3" in our cache (possible versions are ""). This is usually caused by a missing entry in the lockfile, running Yarn without the --offline flag may help fix this issue. info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. To fix this, I decided to apply a patch with the proper `yarn.lock` and the problem is gone now. We should be careful however on the next update, so I added a warning to the `update.sh`-script to remind myself (or whoever will do the next update). I'll leave it as-is now assuming that the issue fixes itself at the next time, a developer runs `yarn`. Also, I'm tired of having to chase dependency errors whenever I touch this package.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions