lune-org/lune
1
1
Fork 0
mirror of https://github.com/lune-org/lune.git synced 2024-12-12 13:00:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Change repository links to new org

Browse source
This commit is contained in:
Filip Tibell 2024-01-14 13:42:10 +01:00
parent 7b4942fc3d
commit ce21063d7c
No known key found for this signature in database
4 changed files with 32 additions and 32 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

36
CHANGELOG.md
View file

@ -98,7 +98,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
}) })
``` ```
[#140]: https://github.com/filiptibell/lune/pull/140 [#140]: https://github.com/lune-org/lune/pull/140
### Changed ### Changed
@ -109,7 +109,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Fixed the `print` and `warn` global functions yielding the thread, preventing them from being used in places such as the callback to `table.sort`. - Fixed the `print` and `warn` global functions yielding the thread, preventing them from being used in places such as the callback to `table.sort`.
- Fixed the `overwrite` option for `fs.move` not correctly removing existing files / directories. ([#133]) - Fixed the `overwrite` option for `fs.move` not correctly removing existing files / directories. ([#133])
[#133]: https://github.com/filiptibell/lune/pull/133 [#133]: https://github.com/lune-org/lune/pull/133
## `0.7.11` - October 29th, 2023 ## `0.7.11` - October 29th, 2023
@ -222,13 +222,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Fixed various functions for `CFrame` in the `roblox` built-in library being incorrect, specifically row-column ordering and some flipped signs. ([#103]) - Fixed various functions for `CFrame` in the `roblox` built-in library being incorrect, specifically row-column ordering and some flipped signs. ([#103])
- Fixed cross-service Instance references disappearing when using the `roblox` built-in library ([#117]) - Fixed cross-service Instance references disappearing when using the `roblox` built-in library ([#117])
[#85]: https://github.com/filiptibell/lune/pull/85 [#85]: https://github.com/lune-org/lune/pull/85
[#93]: https://github.com/filiptibell/lune/pull/93 [#93]: https://github.com/lune-org/lune/pull/93
[#94]: https://github.com/filiptibell/lune/pull/94 [#94]: https://github.com/lune-org/lune/pull/94
[#102]: https://github.com/filiptibell/lune/pull/102 [#102]: https://github.com/lune-org/lune/pull/102
[#103]: https://github.com/filiptibell/lune/pull/103 [#103]: https://github.com/lune-org/lune/pull/103
[#106]: https://github.com/filiptibell/lune/pull/106 [#106]: https://github.com/lune-org/lune/pull/106
[#117]: https://github.com/filiptibell/lune/pull/117 [#117]: https://github.com/lune-org/lune/pull/117
## `0.7.7` - August 23rd, 2023 ## `0.7.7` - August 23rd, 2023
@ -308,9 +308,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Fixed spurious panics and error messages such as `Tried to resume next queued future but none are queued`. - Fixed spurious panics and error messages such as `Tried to resume next queued future but none are queued`.
- Fixed not being able to catch non-string errors properly, errors were accidentally being wrapped in an opaque `userdata` type. - Fixed not being able to catch non-string errors properly, errors were accidentally being wrapped in an opaque `userdata` type.
[#82]: https://github.com/filiptibell/lune/pull/82 [#82]: https://github.com/lune-org/lune/pull/82
[#83]: https://github.com/filiptibell/lune/pull/83 [#83]: https://github.com/lune-org/lune/pull/83
[#86]: https://github.com/filiptibell/lune/pull/86 [#86]: https://github.com/lune-org/lune/pull/86
## `0.7.6` - August 9th, 2023 ## `0.7.6` - August 9th, 2023
@ -405,9 +405,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Fixed not being able to read & write to WebSocket objects at the same time. ([#68]) - Fixed not being able to read & write to WebSocket objects at the same time. ([#68])
- Fixed tab character at the start of a script causing it not to parse correctly. ([#72]) - Fixed tab character at the start of a script causing it not to parse correctly. ([#72])
[#62]: https://github.com/filiptibell/lune/pull/62 [#62]: https://github.com/lune-org/lune/pull/62
[#68]: https://github.com/filiptibell/lune/pull/66 [#68]: https://github.com/lune-org/lune/pull/66
[#72]: https://github.com/filiptibell/lune/pull/72 [#72]: https://github.com/lune-org/lune/pull/72
## `0.7.4` - July 7th, 2023 ## `0.7.4` - July 7th, 2023
@ -425,7 +425,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- When using `roblox.serializeModel`, Lune will no longer keep internal unique ids. <br/> - When using `roblox.serializeModel`, Lune will no longer keep internal unique ids. <br/>
This is consistent with what Roblox does and prevents Lune from always generating a new and unique file. <br/> This is consistent with what Roblox does and prevents Lune from always generating a new and unique file. <br/>
This previously caused unnecessary diffs when using git or other kinds of source control. ([Relevant issue](https://github.com/filiptibell/lune/issues/61)) This previously caused unnecessary diffs when using git or other kinds of source control. ([Relevant issue](https://github.com/lune-org/lune/issues/61))
## `0.7.2` - June 28th, 2023 ## `0.7.2` - June 28th, 2023
@ -450,7 +450,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Fixed `closeCode` erroring when being accessed on websockets. ([#57]) - Fixed `closeCode` erroring when being accessed on websockets. ([#57])
- Fixed issues with `UniqueId` when using the `roblox` builtin by downgrading `rbx-dom`. - Fixed issues with `UniqueId` when using the `roblox` builtin by downgrading `rbx-dom`.
[#57]: https://github.com/filiptibell/lune/pull/57 [#57]: https://github.com/lune-org/lune/pull/57
## `0.7.0` - June 12th, 2023 ## `0.7.0` - June 12th, 2023
@ -519,7 +519,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- Fixed `stdio.write` and `stdio.ewrite` not being flushed and causing output to be interleaved. ([#47]) - Fixed `stdio.write` and `stdio.ewrite` not being flushed and causing output to be interleaved. ([#47])
- Fixed `typeof` returning `userdata` for roblox types such as `Instance`, `Vector3`, ... - Fixed `typeof` returning `userdata` for roblox types such as `Instance`, `Vector3`, ...
[#47]: https://github.com/filiptibell/lune/pull/47 [#47]: https://github.com/lune-org/lune/pull/47
## `0.6.7` - May 14th, 2023 ## `0.6.7` - May 14th, 2023

14
CONTRIBUTING.md
View file

@ -7,14 +7,14 @@
### Reporting a Bug ### Reporting a Bug
- Make sure the bug has not already been reported by searching on GitHub under [Issues](https://github.com/filiptibell/lune/issues). - Make sure the bug has not already been reported by searching on GitHub under [Issues](https://github.com/lune-org/lune/issues).
- If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/filiptibell/lune/issues/new). Be sure to include a **title and description**, as much relevant information as possible, and if applicable, a **code sample** or a **test case** demonstrating the expected behavior. - If you're unable to find an open issue addressing the problem, [open a new one](https://github.com/lune-org/lune/issues/new). Be sure to include a **title and description**, as much relevant information as possible, and if applicable, a **code sample** or a **test case** demonstrating the expected behavior.
--- ---
### Contributing - Bug Fixes ### Contributing - Bug Fixes
1. Make sure an [issue](https://github.com/filiptibell/lune/issues) has been created for the bug first, so that it can be tracked and searched for in the repository history. This is not mandatory for small fixes. 1. Make sure an [issue](https://github.com/lune-org/lune/issues) has been created for the bug first, so that it can be tracked and searched for in the repository history. This is not mandatory for small fixes.
2. Open a new GitHub pull request for it. A pull request for a bug fix must include: 2. Open a new GitHub pull request for it. A pull request for a bug fix must include:
- A clear and concise description of the bug it is fixing. - A clear and concise description of the bug it is fixing.
- A new test file ensuring there are no regressions after the bug has been fixed. - A new test file ensuring there are no regressions after the bug has been fixed.
@ -22,11 +22,11 @@
### Contributing - Features ### Contributing - Features
1. Make sure an [issue](https://github.com/filiptibell/lune/issues) has been created for the feature first, so that it can be tracked and searched for in the repository history. If you are making changes to an existing feature, and no issue exists, one should be created for the proposed changes. 1. Make sure an [issue](https://github.com/lune-org/lune/issues) has been created for the feature first, so that it can be tracked and searched for in the repository history. If you are making changes to an existing feature, and no issue exists, one should be created for the proposed changes.
2. Any API design or considerations should first be brought up and discussed in the relevant issue, to prevent long review times on pull requests and unnecessary work for maintainers. 2. Any API design or considerations should first be brought up and discussed in the relevant issue, to prevent long review times on pull requests and unnecessary work for maintainers.
3. Familiarize yourself with the codebase and the tools you will be using. Some important parts include: 3. Familiarize yourself with the codebase and the tools you will be using. Some important parts include:
- The [mlua](https://crates.io/crates/mlua) library, which we use to interface with Luau. - The [mlua](https://crates.io/crates/mlua) library, which we use to interface with Luau.
- Any [built-in libraries](https://github.com/filiptibell/lune/tree/main/src/lune/builtins) that are relevant for your new feature. If you are making a new built-in library, refer to existing ones for structure and implementation details. - Any [built-in libraries](https://github.com/lune-org/lune/tree/main/src/lune/builtins) that are relevant for your new feature. If you are making a new built-in library, refer to existing ones for structure and implementation details.
- Our toolchain, notably [StyLua](https://github.com/JohnnyMorganz/StyLua), [rustfmt](https://github.com/rust-lang/rustfmt), and [clippy](https://github.com/rust-lang/rust-clippy). If you do not use these tools there is a decent chance CI will fail on your pull request, blocking it from getting approved. - Our toolchain, notably [StyLua](https://github.com/JohnnyMorganz/StyLua), [rustfmt](https://github.com/rust-lang/rustfmt), and [clippy](https://github.com/rust-lang/rust-clippy). If you do not use these tools there is a decent chance CI will fail on your pull request, blocking it from getting approved.
4. Write some code! 4. Write some code!
5. Open a new GitHub pull request. A pull request for a feature must include: 5. Open a new GitHub pull request. A pull request for a feature must include:
@ -48,7 +48,7 @@ Check out the [docs](https://github.com/lune-org/docs) repository and its contri
If type definitions for built-in libraries need improvements: If type definitions for built-in libraries need improvements:
1. Check out the [types](https://github.com/filiptibell/lune/tree/main/types) directory at the root of the repository. 1. Check out the [types](https://github.com/lune-org/lune/tree/main/types) directory at the root of the repository.
2. Make the desired changes, and verify that they have the desired outcome. 2. Make the desired changes, and verify that they have the desired outcome.
3. Open a new GitHub pull request for your changes. 3. Open a new GitHub pull request for your changes.
@ -61,7 +61,7 @@ The Lune release process is semi-automated, and takes care of most things for yo
1. Make sure the changelog is up to date and contains all of the changes since the last release. 1. Make sure the changelog is up to date and contains all of the changes since the last release.
2. Add the release date in the changelog + set a new version number in `Cargo.toml`. 2. Add the release date in the changelog + set a new version number in `Cargo.toml`.
3. Commit and push changes from step 2 to GitHub. This will automatically publish the Lune library to [crates.io](https://crates.io) when the version number changes. 3. Commit and push changes from step 2 to GitHub. This will automatically publish the Lune library to [crates.io](https://crates.io) when the version number changes.
4. Trigger the [release](https://github.com/filiptibell/lune/actions/workflows/release.yaml) workflow on GitHub manually, and wait for it to finish. Find the new pending release in the [Releases](https://github.com/filiptibell/lune/releases) section. 4. Trigger the [release](https://github.com/lune-org/lune/actions/workflows/release.yaml) workflow on GitHub manually, and wait for it to finish. Find the new pending release in the [Releases](https://github.com/lune-org/lune/releases) section.
5. Add in changes from the changelog for the new pending release into the description, hit "accept" on creating a new version tag, and publish 🚀 5. Add in changes from the changelog for the new pending release into the description, hit "accept" on creating a new version tag, and publish 🚀
--- ---

2
Cargo.toml
View file

@ -3,7 +3,7 @@ name = "lune"
version = "0.7.11" version = "0.7.11"
edition = "2021" edition = "2021"
license = "MPL-2.0" license = "MPL-2.0"
repository = "https://github.com/filiptibell/lune" repository = "https://github.com/lune-org/lune"
description = "A standalone Luau runtime" description = "A standalone Luau runtime"
readme = "README.md" readme = "README.md"
keywords = ["cli", "lua", "luau", "runtime"] keywords = ["cli", "lua", "luau", "runtime"]

12
README.md
View file

@ -10,14 +10,14 @@
<a href="https://crates.io/crates/lune"> <a href="https://crates.io/crates/lune">
<img src="https://img.shields.io/crates/v/lune.svg?label=Version" alt="Current Lune library version" /> <img src="https://img.shields.io/crates/v/lune.svg?label=Version" alt="Current Lune library version" />
</a> </a>
<a href="https://github.com/filiptibell/lune/actions"> <a href="https://github.com/lune-org/lune/actions">
<img src="https://shields.io/endpoint?url=https://badges.readysetplay.io/workflow/filiptibell/lune/ci.yaml" alt="CI status" /> <img src="https://shields.io/endpoint?url=https://badges.readysetplay.io/workflow/lune-org/lune/ci.yaml" alt="CI status" />
</a> </a>
<a href="https://github.com/filiptibell/lune/actions"> <a href="https://github.com/lune-org/lune/actions">
<img src="https://shields.io/endpoint?url=https://badges.readysetplay.io/workflow/filiptibell/lune/release.yaml" alt="Release status" /> <img src="https://shields.io/endpoint?url=https://badges.readysetplay.io/workflow/lune-org/lune/release.yaml" alt="Release status" />
</a> </a>
<a href="https://github.com/filiptibell/lune/blob/main/LICENSE.txt"> <a href="https://github.com/lune-org/lune/blob/main/LICENSE.txt">
<img src="https://img.shields.io/github/license/filiptibell/lune.svg?label=License&color=informational" alt="Lune license" /> <img src="https://img.shields.io/github/license/lune-org/lune.svg?label=License&color=informational" alt="Lune license" />
</a> </a>
</div> </div>
</div> </div>