Skip to content

Navigation Menu

Appearance settings

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Appearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

go-gitea / gitea Public

Notifications You must be signed in to change notification settings
Fork 5.9k
Star 49.9k

Code
Issues 2.6k
Pull requests 178
Actions
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Security
Insights

Upgrade to npm lockfile v3 and explicitely set it#23561

Merged

KN4CK3R merged 2 commits intogo-gitea:maingo-gitea/gitea:mainfrom

silverwind:lockfile-3silverwind/gitea:lockfile-3Copy head branch name to clipboard

Mar 18, 2023

Conversation Commits2 (2)Checks Files changed

Merged

Upgrade to npm lockfile v3 and explicitely set it#23561
KN4CK3R merged 2 commits intogo-gitea:mainfrom
silverwind:lockfile-3

Commits

Commits on Mar 18, 2023

Upgrade to npm lockfile v3 and explicitely set it
silverwind
committed
Merge branch 'main' into lockfile-3
delvh
authored

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.