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

yarn.lock outdated on branch version-15? #1947

Closed
1 task done
cogk opened this issue Jul 4, 2024 · 1 comment · Fixed by #2055
Closed
1 task done

yarn.lock outdated on branch version-15? #1947

cogk opened this issue Jul 4, 2024 · 1 comment · Fixed by #2055
Labels
bug Something isn't working released

Comments

@cogk
Copy link
Contributor

cogk commented Jul 4, 2024

Information about bug

https://discuss.frappe.io/t/cannot-proceed-with-update-you-have-local-changes-in-app-hrms-that-are-not-committed/127885/11?u=corentin

fatal: ref refs/remotes/upstream/HEAD is not a symbolic ref

/apps/hrms$ git checkout version-15
M yarn.lock
Already on ‘version-15’
Your branch is up to date with ‘upstream/version-15’.

Interesting if I
git stash in hrms folder the after it I can
bench update

If again I
bench update then NOT WORKING same hrms problem.

Module

other

Version

frappe 15.33.0 version-15
erpnext 15.29.0 version-15
payments 0.0.1 develop
hrms 15.23.0 version-15

Installation method

None

Relevant log output / Stack trace / Full Error Message.

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@cogk cogk added the bug Something isn't working label Jul 4, 2024
@cogk cogk changed the title yarn.lock outdated on branch version-15 yarn.lock outdated on branch version-15? Jul 4, 2024
@frappe-pr-bot
Copy link
Collaborator

🎉 This issue has been resolved in version 15.26.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants