Skip to content

fix(Expense Claim): update ledger entries after updating cost center (backport #2276) #3834

fix(Expense Claim): update ledger entries after updating cost center (backport #2276)

fix(Expense Claim): update ledger entries after updating cost center (backport #2276) #3834

Triggered via pull request October 16, 2024 08:21
Status Success
Total duration 54s
Artifacts

linters.yml

on: pull_request
Semantic Commits
46s
Semantic Commits
Frappe Linter
41s
Frappe Linter
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Frappe Linter
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Frappe Linter
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Semantic Commits
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Semantic Commits
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/