8000 feat: check security service by grutt · Pull Request #639 · hatchet-dev/hatchet · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: check security service #639

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
Merged
merged 11 commits into from
Jun 26, 2024
Merged

feat: check security service #639

merged 11 commits into from
Jun 26, 2024

Conversation

grutt
Copy link
Contributor
@grutt grutt commented Jun 25, 2024

Description

It is desirable to alert users running vulnerable instances

Type of change

  • New feature (non-breaking change which adds functionality)

What's Changed

  • On api start, check the security.onhatchet.run instance for messages relevant to the running version

To Do

  • get the current running version

@vercel Vercel
Copy link
vercel bot commented Jun 25, 2024 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
hatchet-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 26, 2024 8:18pm

@grutt grutt marked this pull request as ready for review June 25, 2024 20:17
abelanger5
abelanger5 requested changes Jun 26, 2024
View reviewed changes
prisma/schema.prisma Outdated
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to run task generate-go

@abelanger5 abelanger5 merged commit a8d4281 into main Jun 26, 2024
25 checks passed
@abelanger5 abelanger5 deleted the feat--security-check branch June 26, 2024 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@abelanger5 abelanger5 abelanger5 approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@grutt @abelanger5
0