Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[master] Release 1.78.2 #2302

Open
wants to merge 21 commits into
base: master
Choose a base branch
from
Open

[master] Release 1.78.2 #2302

wants to merge 21 commits into from

Conversation

gweiying
Copy link
Contributor

Problem

What problem are you trying to solve? What issue does this close?

Closes [insert issue #]

Solution

How did you solve the problem?

Features:

  • Details ...

Improvements:

  • Details ...

Bug Fixes:

  • Details ...

Before & After Screenshots

BEFORE:
[insert screenshot here]

AFTER:
[insert screenshot here]

Tests

What tests should be run to confirm functionality?

Deploy Notes

Notes regarding deployment of the contained body of work. These should note any
new dependencies, new scripts, etc.

New environment variables:

  • env var : env var details

New scripts:

  • script : script details

New dependencies:

  • dependency : dependency details

New dev dependencies:

  • dependency : dependency details

halfwhole and others added 21 commits July 13, 2023 16:04
feat: sgid integration with go
* fix: stored xss via file upload

* chore: refactor tests

* fix: e2e test

* fix: update relative changed file path in e2e
* fix: package.json to reduce vulnerabilities

---------

Co-authored-by: snyk-bot <snyk-bot@snyk.io>
Co-authored-by: PikkaPikkachu <prakriti_bansal@yahoo.com>
* build(deps): bump node from 16 to 18

* build: bump testcafe to 2.6.2, typescript to 4.7.4, and downstream fixes
* chore: replace query to check if shortlink is available

* chore: add tests

* chore: make return more readable
@gweiying gweiying changed the title Release 1.78.2 [master] Release 1.78.2 Mar 18, 2024
return
} catch (error) {
logger.error(error)
res.status(500).render('error', { error })

Check warning

Code scanning / CodeQL

Information exposure through a stack trace Medium

This information exposed to the user depends on
stack trace information
.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants