-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
docs: fix link to email, when vulnerability found #11667
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
Conversation
gioboa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your help @pkuczynski
I think we should add the new management.
cc @michaelbromley @dlhck
|
I thought so too, but at least short term this PR is helping to find the email. Long term I guess this should move more to the documentation and use some more generic email. I will leave this up to you to figure out :) |
gioboa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks 🙏
|
Maybe we should add put in place a |
gioboa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It sounds great 👍
commit: |
|
Sure! Good idea. Done... |
|
Failing build step is not relevant to my changes... |
Yeah, the Coveralls APIs are not very reliable, their service has <99% availability, so often coverage reporting fails. Thanks for the update :) |
WalkthroughThis PR updates the project's security contact information and maintainer metadata. The CONTRIBUTING.md file is updated to reference a dedicated maintainer email for security vulnerabilities, and package.json is updated to reflect TypeORM as the author with a shared maintainers email address. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (2)
🧰 Additional context used🧠 Learnings (1)📚 Learning: 2025-07-27T17:29:18.547ZApplied to files:
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (20)
🔇 Additional comments (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
gioboa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this ❤️
* docs: fix link to email, when vulnerability found * Update package.json * Update CONTRIBUTING.md --------- Co-authored-by: Giorgio Boa <35845425+gioboa@users.noreply.github.com>
* docs: fix link to email, when vulnerability found * Update package.json * Update CONTRIBUTING.md --------- Co-authored-by: Giorgio Boa <35845425+gioboa@users.noreply.github.com>
Not sure if this is a good long term strategy, but at least it fixes docs issue...
Summary by CodeRabbit
Documentation
Chores