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.

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

[Update Request]: Stretchly 1.17.2 #219075

Closed
rpmrmartin opened this issue Jan 29, 2025 · 2 comments · Fixed by #219253
Closed

[Update Request]: Stretchly 1.17.2 #219075

rpmrmartin opened this issue Jan 29, 2025 · 2 comments · Fixed by #219253
Labels
In-PR Package-Update This package needs to be updated

Comments

@rpmrmartin
Copy link

What type of update are you requesting?

A new version of an existing package

Current Package Identifier

Stretchly.Stretchly

Package Version

1.17.2

Please describe the changes you would like to see

There is a new release (1.17.2) available.
Download page URL: https://github.com/hovancik/stretchly/releases

@rpmrmartin rpmrmartin added Help-Wanted This is a good candidate work item from the community. Package-Update This package needs to be updated labels Jan 29, 2025
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage This work item needs to be triaged by a member of the core team. label Jan 29, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added In-PR and removed Help-Wanted This is a good candidate work item from the community. Needs-Triage This work item needs to be triaged by a member of the core team. labels Jan 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
In-PR Package-Update This package needs to be updated
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants