Skip to content

Conversation

@LucasMMota
Copy link
Contributor

Why? πŸ“–

Release version 1.0.7

What? πŸ”§

Fixed
Update Workflow runner - #71

Type of change πŸ—„οΈ

  • Release

Checklist πŸ“

  • I have added labels to distinguish the type of pull request.
  • My code follows the style guidelines of this project (docstrings, type hinting and linter compliance);
  • I have performed a self-review of my own code;
  • I have made corresponding changes to the documentation;
  • I have added tests that prove my fix is effective or that my feature works;
  • I have made sure that new and existing unit tests pass locally with my changes;

Attention Points ⚠️

Replace me for what the reviewer will need to pay attention to in the PR or just to cover any concerns after the merge.

@LucasMMota LucasMMota self-assigned this Aug 11, 2022
@LucasMMota LucasMMota changed the base branch from main to lucas/fix-ci August 11, 2022 14:05
@LucasMMota LucasMMota changed the title Lucasmendes/release 1 0 10 Release 1.0.10 Aug 11, 2022
@LucasMMota LucasMMota force-pushed the lucasmendes/release-1-0-10 branch from f95d0cc to e7f7cb6 Compare August 11, 2022 14:19
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!Β  Β  Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Base automatically changed from lucas/fix-ci to main August 17, 2022 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants