pengtaihao
/
ParticleEffectForUGUI
mirror of https://github.com/mob-sakai/ParticleEffectForUGUI
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Render particle effect in UnityUI(uGUI). Maskable, sortable, and no extra Camera/RenderTexture/Canvas.
311 Commits
10 Branches
104 Tags
26 MiB
C# 98.1%
ShaderLab 1.9%
 
 
Go to file
semantic-release-bot 01e08eefbd chore(release): 4.6.4 [skip ci] 
## [4.6.4](https://github.com/mob-sakai/ParticleEffectForUGUI/compare/v4.6.3...v4.6.4) (2024-05-22)

### Bug Fixes

* assertion failed on expression: 'ps->array_size()' ([1b5c359](1b5c359058)), closes [#278](https://github.com/mob-sakai/ParticleEffectForUGUI/issues/278)
* lost Material.mainTexture when using AnimatableProperties ([ea04352](ea043524c0)), closes [#311](https://github.com/mob-sakai/ParticleEffectForUGUI/issues/311)
* remove unnecessary code ([c37c014](c37c014864))
 		2024-05-22 10:53:55 +00:00
.github/workflows chore: fix release workflow 2024-05-22 19:53:16 +09:00
Assets demo: update demos 2024-02-01 17:42:50 +09:00
Packages chore(release): 4.6.4 [skip ci] 2024-05-22 10:53:55 +00:00
ProjectSettings fix: fix demos 2024-02-01 16:18:17 +09:00
.editorconfig init 2024-01-23 14:54:17 +09:00
.gitignore init 2024-01-23 14:54:17 +09:00
README.md docs: fix readme 2023-11-21 11:55:34 +09:00

README.md

🛠 Package Development

NOTE: This branch is for development purposes only.

Develop the Package with the develop Branch

  1. Fork the repository.

  2. Clone the repository.

  3. Checkout develop branch.

  4. Develop the package.

  5. Test the package with the test runner (Window > Generals > Test Runner).

  6. Commit with a message based on Angular Commit Message Conventions as follows:

    • fix: fix a bug
    • feat: new feature
    • docs: changes only in documentation
    • style: changes only in formatting, white-space, etc
    • refactor: changes only in code structure (extract method, rename variable, move method, etc)
    • perf: changes only in code performance
    • test: add or update tests
    • chore: changes to the build process or auxiliary tools and libraries such as documentation generation

  7. Create a pull request on GitHub. Fill out the description, link any related issues and submit your pull request.

For details, refer to CONTRIBUTING and CODE_OF_CONDUCT.

How to Release This Package

When you push to the preview, release, or v4.x branch, this package is automatically released by GitHub Action.

Semantic Release is used for automatic release.

  • Update the version in package.json.
  • Update CHANGELOG.md.
  • Commit documents and push.
  • Update and tag the UPM branch.
  • Release on GitHub.
  • Publish npm registry

Alternatively, you can release it manually with the following command:

$ cd Packages/src
$ npm run release -- --no-ci