Skip to content
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

New version: Mega.MEGASync version 4.11.0.0 #133712

Merged
merged 1 commit into from
Jan 11, 2024
Merged

New version: Mega.MEGASync version 4.11.0.0 #133712

merged 1 commit into from
Jan 11, 2024

Conversation

fancybody
Copy link
Contributor

@fancybody fancybody commented Jan 11, 2024 •
edited
Loading

  • Have you signed the Contributor License Agreement?
  • Have you checked that there aren't other open pull requests for the same manifest update/change?
  • This PR only modifies one (1) manifest
  • Have you validated your manifest locally with winget validate --manifest <path>?
  • Have you tested your manifest locally with winget install --manifest <path>?
  • Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Resolves #133696

Microsoft Reviewers: Open in CodeFlow

@wingetbot
Copy link
Collaborator

Service Badge  Service Badge  

@wingetbot
Copy link
Collaborator

/AzurePipelines run

@azure-pipelines Azure Pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@wingetbot wingetbot added Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Completed Validation passed Possible-Duplicate labels Jan 11, 2024
@wingetbot
Copy link
Collaborator

Possible duplicate package entry.

Similar installer SHA256 hash found in manifest:

  • InstallerSha256: e7fdbe6beb1ec7fc3b7b838e11cd1ffd9ad0f907e43e6acf6e499074a01938db
    • manifests\m\Mega\MEGASync\4.10.0.0
  • InstallerSha256: 698524e57cb0e7d9bc9c13c188b681e6a9c218b80dd7db32420a7c0fbf72f6b9
    • manifests\m\Mega\MEGASync\4.10.0.0

@stephengillie
Copy link
Collaborator

Possible duplicate package entry.

Similar installer SHA256 hash found in manifest:

  • InstallerSha256: e7fdbe6beb1ec7fc3b7b838e11cd1ffd9ad0f907e43e6acf6e499074a01938db

    • manifests\m\Mega\MEGASync\4.10.0.0

  • InstallerSha256: 698524e57cb0e7d9bc9c13c188b681e6a9c218b80dd7db32420a7c0fbf72f6b9

    • manifests\m\Mega\MEGASync\4.10.0.0

Hi @fancybody,

Did Mega re-release the 4.10.0.0 version as 4.11.0.0?

@stephengillie stephengillie added the Needs-Author-Feedback This needs a response from the author. label Jan 11, 2024
@fancybody
Copy link
Contributor Author

@stephengillie

Installing it from official website shows 4.11.0 inside the application.
megasync

Comparing the release time of 4.11.0.0 source release and commit time of 4.10.0.0 manifest #126594, show a 5 hour gap.
My commit just fixes the version number.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention This work item needs to be reviewed by a member of the core team. and removed Needs-Author-Feedback This needs a response from the author. labels Jan 11, 2024
@stephengillie stephengillie removed Possible-Duplicate Needs-Attention This work item needs to be reviewed by a member of the core team. labels Jan 11, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot merged commit 92aabba into microsoft:master Jan 11, 2024
8 checks passed
@microsoft-github-policy-service microsoft-github-policy-service bot added the Moderator-Approved One of the Moderators has reviewed and approved this PR label Jan 11, 2024
@fancybody fancybody deleted the Mega.MEGASync-4.11.0.0 branch January 11, 2024 19:08
@wingetbot
Copy link
Collaborator

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

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

@stephengillie stephengillie stephengillie approved these changes

Assignees
No one assigned
Labels
Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Moderator-Approved One of the Moderators has reviewed and approved this PR Publish-Pipeline-Succeeded Validation-Completed Validation passed
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Update Request]: Mega.MEGASync
3 participants
@fancybody @wingetbot @stephengillie