5 Commits (2d2a5657eff303b96c1168a4994215c4a0419387)

Author	SHA1	Message	Date
Giteabot	e9fcdf822c	Update JS and Poetry dependencies and eslint (#27200) (#27201) ... Backport #27200 by @silverwind - Update all JS and Poetry dependencies - Remove deprecated `eslint-plugin-custom-elements` and replace it with rules from `eslint-plugin-wc` - Add a convenience `make update` to update both js and py dependencies - Tested markdown toolbar, swagger and citation Co-authored-by: silverwind <me@silverwind.io>	1 year ago
Chongyi Zheng	7046065c0e	Drop Node.js 16 and update js dependencies (#27094) ... - Drop Node.js 16 since it reached EOL - Upgrade js dependencies - Two packages have major version bump - `updates`: require node 18 - `eslint-plugin-array-func`: require `eslint` 8.40.0, which is satisfied - Run `make svg` for `@primer/octicons` update	1 year ago
silverwind	5feef6d5c0	Update JS dependencies (#26586) ... - Update all JS dependencies - Adapt `ansi_up` import for ESM - Tested Mermaid and Ansi rendering	1 year ago
silverwind	8e644d3460	Update js and py dependencies (#26243) ... - Update all JS and PY dependencies minus `eslint-plugin-eslint-comments` (because of https://github.com/eslint-community/eslint-plugin-eslint-comments/issues/89) - Regenerate SVGs - Remove depreacted eslint rule - Tested mermaid and swagger	1 year ago
wxiaoguang	faa28b5a44	Move public asset files to the proper directory (#25907) ... Move `public/*` to `public/assets/*` Some old PRs (like #15219) introduced inconsistent directory system. For example: why the local directory "public" is accessed by `http://site/assets`? How to serve the ".well-known" files properly in the public directory? For convention rules, the "public" directory is widely used for the website's root directory. It shouldn't be an exception for Gitea. So, this PR makes the things consistent: * `http://site/assets/foo` means `{CustomPath}/public/assets/foo`. * `{CustomPath}/public/.well-known` and `{CustomPath}/public/robots.txt` can be used in the future. This PR is also a prerequisite for a clear solution for: * #21942 * #25892 * discourse.gitea.io: [.well-known path serving custom files behind proxy?](https://discourse.gitea.io/t/well-known-path-serving-custom-files-behind-proxy/5445/1) This PR is breaking for users who have custom "public" files (CSS/JS). After getting approvals, I will update the documents. ---- ## ⚠️ BREAKING ⚠️ If you have files in your "custom/public/" folder, please move them to "custom/public/assets/". --------- Co-authored-by: 6543 <6543@obermui.de> Co-authored-by: Giteabot <teabot@gitea.io>	1 year ago