Skip to content

[BED-4714] Version bump for pipeline update release #144

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 1 commit into from
Apr 3, 2025
Merged

[BED-4714] Version bump for pipeline update release #144

merged 1 commit into from
Apr 3, 2025

Conversation

definitelynotagoblin
Copy link
Contributor

Description

Version bump for new pipeline release

Motivation and Context

https://specterops.atlassian.net/browse/BED-4714

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Chore (a change that does not modify the application functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • Documentation updates are needed, and have been made accordingly.
  • I have added and/or updated tests to cover my changes.
  • All new and existing tests passed.
  • My changes include a database migration.

@definitelynotagoblin definitelynotagoblin added the enhancement New feature or request label Apr 3, 2025
@definitelynotagoblin definitelynotagoblin merged commit a5fc2ae into 2.X Apr 3, 2025
1 check passed
@definitelynotagoblin definitelynotagoblin deleted the v2-6-3 branch April 3, 2025 21:49
@github-actions github-actions bot locked and limited conversation to collaborators Apr 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@sircodemane sircodemane sircodemane approved these changes

Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@definitelynotagoblin @sircodemane