Skip to content

Update jitpack.yml#392

Merged
NorbertKlockiewicz merged 1 commit intomainfrom
@nk/update-jitpack-path
Jun 12, 2025
Merged

Update jitpack.yml#392
NorbertKlockiewicz merged 1 commit intomainfrom
@nk/update-jitpack-path

Conversation

@NorbertKlockiewicz
Copy link
Copy Markdown
Contributor

Description

Update jitpack.yml so the package won't cause errors on android

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update (improves or adds clarity to existing documentation)

Tested on

  • iOS
  • Android

Testing instructions

Screenshots

Related issues

Checklist

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have updated the documentation accordingly
  • My changes generate no new warnings

Additional notes

Update jitpack.yml so the package won't cause errors on android
@NorbertKlockiewicz NorbertKlockiewicz merged commit 131121d into main Jun 12, 2025
2 checks passed
@NorbertKlockiewicz NorbertKlockiewicz deleted the @nk/update-jitpack-path branch June 12, 2025 13:34
mkopcins pushed a commit that referenced this pull request Oct 15, 2025
## Description

Update jitpack.yml so the package won't cause errors on android

### Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation update (improves or adds clarity to existing
documentation)

### Tested on

- [ ] iOS
- [ ] Android

### Testing instructions

<!-- Provide step-by-step instructions on how to test your changes.
Include setup details if necessary. -->

### Screenshots

<!-- Add screenshots here, if applicable -->

### Related issues

<!-- Link related issues here using #issue-number -->

### Checklist

- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have updated the documentation accordingly
- [ ] My changes generate no new warnings

### Additional notes

<!-- Include any additional information, assumptions, or context that
reviewers might need to understand this PR. -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants