Skip to content

Navigation Menu

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.

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

RayTale / Vertex Public

Notifications You must be signed in to change notification settings
Fork 42
Star 285

Code
Issues 2
Pull requests 6
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Back to pull request #217

Version number update and compatibility upgrade of dependent libraries #446

Sign in to view logs

Sign in to view logs

Version number update and compatibility upgrade of dependent libraries

Version number update and compatibility upgrade of dependent libraries #446

Summary
Jobs
- build
Run details
- Usage
- Workflow file

Usage Workflow file

Annotations

12 warnings

The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Build: src/Vertex.Protocol/EventConverter.cs.cs#L2

Elements should have the same indentation (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1137.md)

Build: src/Vertex.Protocol/EventConverter.cs.cs#L3

Elements should have the same indentation (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1137.md)

Build: src/Vertex.Protocol/EventConverter.cs.cs#L5

Elements should have the same indentation (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1137.md)

Build: src/Vertex.Runtime/Serialization/EventTypeContainer.cs#L2

Elements should have the same indentation (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1137.md)

Build: src/Vertex.Runtime/Serialization/EventTypeContainer.cs#L3

Elements should have the same indentation (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1137.md)

Build: src/Vertex.Runtime/Serialization/EventTypeContainer.cs#L4

Elements should have the same indentation (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1137.md)

Build: src/Vertex.Runtime/Serialization/EventTypeContainer.cs#L5

Elements should have the same indentation (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1137.md)

Build: src/Vertex.Runtime/Serialization/EventTypeContainer.cs#L6

Elements should have the same indentation (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1137.md)

Build: src/Vertex.Runtime/Serialization/EventTypeContainer.cs#L8

Elements should have the same indentation (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1137.md)

Found version-specific or distribution-specific runtime identifier(s): alpine-x64. Affected libraries: SQLitePCLRaw.lib.e_sqlite3. In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.

build

succeeded Oct 28, 2024 in 2m 12s

Loading

Re-running jobs...

You can’t perform that action at this time.