Skip to content

Conversation

@praveenkuttappan
Copy link
Member

Update package version on API revision even if API surface matches to reflect correct package version info. This change along with tagging a revision after package release will ensure that package version is updated correctly(A separate change from updating package version).

@praveenkuttappan praveenkuttappan added APIView Issues related to APIView core functionality or UI Central-EngSys This issue is owned by the Engineering System team. labels Mar 5, 2024
@praveenkuttappan praveenkuttappan self-assigned this Mar 5, 2024
@praveenkuttappan
Copy link
Member Author

@chidozieononiwu @maririos I have pushed additional changes to update label and also to add a new package version param to send actual package version instead of daily build alpha version from CI. I have fixed another issue in copying approval status to automatic review.


[HttpPost]
public async Task<ActionResult> UploadAutoReview([FromForm] IFormFile file, string label, bool compareAllRevisions = false)
public async Task<ActionResult> UploadAutoReview([FromForm] IFormFile file, string label, bool compareAllRevisions = false, string packageVersion = null)
Copy link
Member

Choose a reason for hiding this comment

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

would it be helpful to document in which cases the function expects packageVersion not to be null?

Copy link
Member Author

Choose a reason for hiding this comment

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

I added it as null for now until all individual caller from language repo starts to send it. Once change is merged to individual repos, I will change this as required param.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

APIView Issues related to APIView core functionality or UI Central-EngSys This issue is owned by the Engineering System team.

Projects

Status: ✅ Done
Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants