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.

Sign up for GitHub

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

Jump to bottom

Snyk upgrade 708684d5af8a27c234e6317ae95b4c36 #36220

Closed
wants to merge 4 commits into from
Closed

Snyk upgrade 708684d5af8a27c234e6317ae95b4c36 #36220

wants to merge 4 commits into from

Conversation

nafeef123
Copy link

Why:

Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the preview environment.

snyk-bot and others added 4 commits January 4, 2025 01:45
@snyk-bot
fix: upgrade @babel/runtime from 7.11.2 to 7.26.0
49305d1 
Snyk has created this PR to upgrade @babel/runtime from 7.11.2 to 7.26.0.

See this package in npm:
@babel/runtime

See this project in Snyk:
https://app.snyk.io/org/nafeef123/project/5cb99d32-ec63-4ad1-9035-7f12be99d135?utm_source=github&utm_medium=referral&page=upgrade-pr
@nafeef123
Merge pull request #5 from nafeef123/snyk-upgrade-0de01c3a9662e9a2e82…
14d5653 
…e26cfeff19f4b

[Snyk] Upgrade @babel/runtime from 7.11.2 to 7.26.0
@snyk-bot
fix: upgrade @babel/plugin-transform-runtime from 7.11.0 to 7.25.9
b4172e2 
Snyk has created this PR to upgrade @babel/plugin-transform-runtime from 7.11.0 to 7.25.9.

See this package in npm:
@babel/plugin-transform-runtime

See this project in Snyk:
https://app.snyk.io/org/nafeef123/project/5cb99d32-ec63-4ad1-9035-7f12be99d135?utm_source=github&utm_medium=referral&page=upgrade-pr
@nafeef123
Create npm-publish-github-packages.yml
6c76ac5
@welcome Welcome
Copy link

welcome bot commented Feb 8, 2025

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Feb 8, 2025

🚀 Manual Deployment Required

It looks like this pull request contains code changes. To preview these changes, an internal Hubber will need to manually deploy the changes to one of our staging servers.

Thank you for your contribution!

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Feb 8, 2025
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Feb 8, 2025

👋 Hey there spelunker. It looks like you've modified some files that we can't accept as contributions:

  • .github/workflows/npm-publish-github-packages.yml
  • package-lock.json
  • package.json

You'll need to revert all of the files you changed that match that list using GitHub Desktop or git checkout origin/main <file name>. Once you get those files reverted, we can continue with the review process. :octocat:

The complete list of files we can't accept are:

  • .devcontainer/**
  • .github/**
  • data/reusables/rai/**
  • Dockerfile*
  • src/**
  • package*.json
  • content/actions/deployment/security-hardening-your-deployments/**

We also can't accept contributions to files in the content directory with frontmatter type: rai.

@subatoi subatoi added the invalid This issue/PR is invalid label Feb 10, 2025
@github-actions github-actions bot closed this Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
invalid This issue/PR is invalid triage Do not begin working on this issue until triaged by the team
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@nafeef123 @subatoi @snyk-bot